[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120619080109.b28055c1b32fb81027a9562b@canb.auug.org.au>
Date: Tue, 19 Jun 2012 08:01:09 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Randy Dunlap <rdunlap@...otime.net>
Cc: linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Kay Sievers <kay@...y.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: linux-next: Tree for Jun 18 (kmsg problems)
[Adding Greg and Kay]
On Mon, 18 Jun 2012 10:13:11 -0700 Randy Dunlap <rdunlap@...otime.net> 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@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists