Re: linux-next: Tree for Jun 18 (kmsg problems)

[Stephen Rothwell]

[Adding Greg and Kay]

On Mon, 18 Jun 2012 10:13:11 -0700 Randy Dunlap <rdunlap@xxxxxxxxxxxx> wrote:
>
> on x86_64:
> 
> arch/x86/kernel/reboot.o: In function `kmsg_dump_get_line':
> reboot.c:(.text+0xf0): multiple definition of `kmsg_dump_get_line'
> arch/x86/kernel/setup.o:setup.c:(.text+0x0): first defined here
> arch/x86/kernel/reboot.o: In function `kmsg_dump_get_buffer':
> reboot.c:(.text+0x100): multiple definition of `kmsg_dump_get_buffer'
> arch/x86/kernel/setup.o:setup.c:(.text+0x10): first defined here
> arch/x86/kernel/reboot.o: In function `kmsg_dump_rewind':
> reboot.c:(.text+0x110): multiple definition of `kmsg_dump_rewind'
> arch/x86/kernel/setup.o:setup.c:(.text+0x20): first defined here

Caused by commit e2ae715d66bf ("kmsg - kmsg_dump() use iterator to
receive log buffer content") from the driver-core.current tree.

This was reported a few days ago.  Why is it not fixed yet?  Especially
since it is in a branch that is supposedly "bug fixes"?

-- 
Cheers,
Stephen Rothwell                    sfr@xxxxxxxxxxxxxxxx

Attachment: pgp00000.pgp
Description: PGP signature