From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-staging/linux-next merge/build errors
Date: Sat, 21 Jun 2008 00:10:23 -0700 [thread overview]
Message-ID: <20080621071023.GA2765@kroah.com> (raw)
In-Reply-To: <20080621124017.ec3b0a51.sfr@canb.auug.org.au>
On Sat, Jun 21, 2008 at 12:40:17PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today I have done a test merge of linux-staging into linux-next. I got
> merge conflicts in drivers/char/agp/via-agp.c and drivers/misc/Makefile -
> neither of which is really surprising and both tivial to fix up.
>
> I then did an x86 allmodconfig build with these errors:
>
> In file included from /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_drm.c:32:
> /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_3d_reg.h: In function ‘IS_AGPHEADER_INV’:
> /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_3d_reg.h:230: error: ‘TRUE’ undeclared (first use in this function)
> /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_3d_reg.h:230: error: (Each undeclared identifier is reported only once
> /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_3d_reg.h:230: error: for each function it appears in.)
> /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_3d_reg.h:232: error: ‘FALSE’ undeclared (first use in this function)
Wierd, this passes allmodconfig on i386, something else must be
declaring TRUE and FALSE :)
I'll just go remove them entirely.
> And several new warnings (these may not be all):
>
> /home/sfr/kernels/next/src/fs/novfs/inode.c:265: warning: initialization from incompatible pointer type
> /home/sfr/kernels/next/src/fs/novfs/inode.c:267: warning: initialization from incompatible pointer type
> /home/sfr/kernels/next/src/fs/novfs/inode.c:273: warning: initialization from incompatible pointer type
> /home/sfr/kernels/next/src/fs/novfs/inode.c:275: warning: initialization from incompatible pointer type
> In file included from /home/sfr/kernels/next/src/fs/novfs/daemon.c:24:
> include2/asm/semaphore.h:1:2: warning: #warning Use linux/semaphore.h, not asm/semaphore.h
> In file included from /home/sfr/kernels/next/src/fs/novfs/scope.c:26:
> include2/asm/semaphore.h:1:2: warning: #warning Use linux/semaphore.h, not asm/semaphore.h
> In file included from /home/sfr/kernels/next/src/fs/novfs/nwcapi.c:22:
> include2/asm/semaphore.h:1:2: warning: #warning Use linux/semaphore.h, not asm/semaphore.h
Yeah, we took a major update of novfs and some of my previous fixes like
this got lost.
I'll go resolve them now.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-staging/linux-next merge/build errors
Date: Sat, 21 Jun 2008 00:10:23 -0700 [thread overview]
Message-ID: <20080621071023.GA2765@kroah.com> (raw)
In-Reply-To: <20080621124017.ec3b0a51.sfr@canb.auug.org.au>
On Sat, Jun 21, 2008 at 12:40:17PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today I have done a test merge of linux-staging into linux-next. I got
> merge conflicts in drivers/char/agp/via-agp.c and drivers/misc/Makefile -
> neither of which is really surprising and both tivial to fix up.
>
> I then did an x86 allmodconfig build with these errors:
>
> In file included from /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_drm.c:32:
> /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_3d_reg.h: In function ‘IS_AGPHEADER_INV’:
> /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_3d_reg.h:230: error: ‘TRUE’ undeclared (first use in this function)
> /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_3d_reg.h:230: error: (Each undeclared identifier is reported only once
> /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_3d_reg.h:230: error: for each function it appears in.)
> /home/sfr/kernels/next/src/drivers/char/drm/via_chrome9_3d_reg.h:232: error: ‘FALSE’ undeclared (first use in this function)
Wierd, this passes allmodconfig on i386, something else must be
declaring TRUE and FALSE :)
I'll just go remove them entirely.
> And several new warnings (these may not be all):
>
> /home/sfr/kernels/next/src/fs/novfs/inode.c:265: warning: initialization from incompatible pointer type
> /home/sfr/kernels/next/src/fs/novfs/inode.c:267: warning: initialization from incompatible pointer type
> /home/sfr/kernels/next/src/fs/novfs/inode.c:273: warning: initialization from incompatible pointer type
> /home/sfr/kernels/next/src/fs/novfs/inode.c:275: warning: initialization from incompatible pointer type
> In file included from /home/sfr/kernels/next/src/fs/novfs/daemon.c:24:
> include2/asm/semaphore.h:1:2: warning: #warning Use linux/semaphore.h, not asm/semaphore.h
> In file included from /home/sfr/kernels/next/src/fs/novfs/scope.c:26:
> include2/asm/semaphore.h:1:2: warning: #warning Use linux/semaphore.h, not asm/semaphore.h
> In file included from /home/sfr/kernels/next/src/fs/novfs/nwcapi.c:22:
> include2/asm/semaphore.h:1:2: warning: #warning Use linux/semaphore.h, not asm/semaphore.h
Yeah, we took a major update of novfs and some of my previous fixes like
this got lost.
I'll go resolve them now.
thanks,
greg k-h
next prev parent reply other threads:[~2008-06-21 7:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 2:40 linux-staging/linux-next merge/build errors Stephen Rothwell
2008-06-21 7:10 ` Greg KH [this message]
2008-06-21 7:10 ` Greg KH
2008-06-21 7:19 ` How linux-staging is released (was Re: linux-staging/linux-next merge/build errors) Greg KH
2008-06-21 13:00 ` Peter Zijlstra
2008-06-21 17:50 ` Greg KH
2008-06-21 18:02 ` Peter Zijlstra
2008-06-21 21:50 ` Greg KH
2008-06-26 12:30 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080621071023.GA2765@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.