linux-kernel - Re: linux-next: build failure after merge of the staging tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 3 May 2010 18:17:21 +0200
From:	Tobias Klauser <tklauser@...tanz.ch>
To:	Greg KH <greg@...ah.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the staging tree

On 2010-04-28 at 17:28:09 +0200, Greg KH <greg@...ah.com> wrote:
> On Wed, Apr 28, 2010 at 04:14:25PM +1000, Stephen Rothwell wrote:
> > Hi Greg,
> > 
> > On Tue, 27 Apr 2010 08:13:05 -0700 Greg KH <greg@...ah.com> wrote:
> > >
> > > On Tue, Apr 27, 2010 at 02:12:24PM +1000, Stephen Rothwell wrote:
> > > > 
> > > > After merging the staging tree, today's linux-next build (x86_64
> > > > allmodconfig) failed like this:
> > > > 
> > > > ERROR: "uart_console_device" [drivers/serial/altera_uart.ko] undefined!
> > > > ERROR: "uart_console_device" [drivers/serial/altera_jtaguart.ko] undefined!
> > > > 
> > > > Introduced by commits 76bdbd933febe791fee114e7bb6c42bbd1a3f4f3 ("serial:
> > > > Add driver for the Altera UART") and
> > > > 11c59b34b299d7214b466cf799410a9a540476e3 ("serial: Add driver for the
> > > > Altera JTAG UART").
> > > > 
> > > > I have reverted those commits for today.
> > > 
> > > Those came in through the tty quilt tree, not the staging tree, right?
> > 
> > Yeah, I just don't do a build between merging the tty and staging trees.
> 
> Ok, that makes sense.
> 
> > > Tobias, care to send me a patch to resolve this?  I already fixed one
> > > Kconfig issue in these patches (forcing the driver to always be built
> > > in.)  Is that what caused this symbol issue?
> > 
> > I have reverted those commits again today.
> 
> I think I'll go drop these patches now.  Tobias, care to resend them
> when you have them working properly?

I just built the current linux-next (20100503) with the patches applied
(including Greg's Kconfig change) on x86_64 with allmodconfig and wasn't
able to reproduce the build failure.

Any pointers on how to reproduce and/or fix this would be appreciated.

Thanks,
Tobias
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/