Subject: Re: linux-next: build failure after merge of the tty tree

From: Randy Dunlap <[email-masked]>
Date: Thu, 23 Sep 2010 10:13:54 -0700

On Thu, 23 Sep 2010 18:12:12 +0100 Alan Cox wrote:

> On Thu, 23 Sep 2010 08:13:50 -0700
> Randy Dunlap <[email-masked]> 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).

True.  But linux-next is mostly to test the merger of lots of trees.

BTW, all{mod,yes}config sets CONFIG_STAGING=y and CONFIG_STAGING_EXCLUDE_BUILD=y,
so the above shouldn't show up in an all*config build.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***