From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
"David S. Miller" <davem@davemloft.net>
Subject: linux-next: net/wireless tree build failure
Date: Tue, 9 Jun 2009 23:33:57 +1000 [thread overview]
Message-ID: <20090609233357.5d3801a0.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
Hi John, Dave,
Today's linux-next build (pmac32 defconfig) failed like this:
In file included from drivers/net/wireless/b43/phy_common.h:5,
from drivers/net/wireless/b43/phy_common.c:30:
include/linux/rfkill.h: In function 'rfkill_alloc':
include/linux/rfkill.h:279: error: implicit declaration of function 'ERR_PTR'
include/linux/rfkill.h:279: warning: return makes pointer from integer without a cast
include/linux/rfkill.h: In function 'rfkill_register':
include/linux/rfkill.h:284: warning: comparison between pointer and integer
In file included from include/linux/dma-mapping.h:6,
from arch/powerpc/include/asm/pci.h:16,
from include/linux/pci.h:1101,
from include/linux/ssb/ssb.h:9,
from drivers/net/wireless/b43/b43.h:9,
from drivers/net/wireless/b43/phy_common.c:35:
include/linux/err.h: At top level:
include/linux/err.h:22: error: conflicting types for 'ERR_PTR'
include/linux/rfkill.h:279: note: previous implicit declaration of 'ERR_PTR' was here
Probably caused by commit 19d337dff95cbf76edd3ad95c0cee2732c3e1ec5
("rfkill: rewrite") which added uses of ERR_PTR to inlines in rfkill.h
but did not include linux/err.h.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-06-09 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 13:33 Stephen Rothwell [this message]
2009-06-09 13:54 ` Johannes Berg
2009-06-09 14:02 ` Stephen Rothwell
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=20090609233357.5d3801a0.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®