[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100923181212.422e76c1@lxorguk.ukuu.org.uk>
Date: Thu, 23 Sep 2010 18:12:12 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Randy Dunlap <rdunlap@...otime.net>
Cc: Greg KH <greg@...ah.com>, Stephen Rothwell <sfr@...b.auug.org.au>,
Alan Cox <alan@...ux.intel.com>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the tty tree
On Thu, 23 Sep 2010 08:13:50 -0700
Randy Dunlap <rdunlap@...otime.net> wrote:
> On Thu, 23 Sep 2010 07:14:33 -0700 Greg KH wrote:
>
> > On Thu, Sep 23, 2010 at 02:20:18PM +1000, Stephen Rothwell wrote:
> > > Hi Greg,
> > >
> > > After merging the tty tree, today's linux-next build (x86_64
> > > allmodconfig) failed like this:
> > >
> > > drivers/char/ip2/ip2main.c:459: error: 'ip2_get_icount' undeclared here (not in a function)
> > >
> > > Caused by commit 157be28e51ed476aa357c8718aaef4832f4da66b ("tty: icount
> > > changeover for other main devices").
> > >
> > > Please build test (especially the trivial "cut and paste" changes) ...
> > >
> > > I have reverted that commit for today.
> >
> > Ick, sorry about that. Alan, care to send a fixup patch for this?
>
>
> So developers and maintainers are not doing allmodconfig builds?
> I can understand not doing randconfig builds.
drivers/staging/ti-st/st_kim.c:34:20: error: st_kim.h: No such file or
directory
So there isn't actually much point trying allmodconfig builds (thats not
the only fail either).
--
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/
Powered by blists - more mailing lists