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,
Arend van Spriel <arend@broadcom.com>,
Pieter-Paul Giesberts <pieterpg@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>
Subject: linux-next: build failure after merge of the final tree (wireless-next tree related)
Date: Thu, 21 Jun 2012 15:59:11 +1000 [thread overview]
Message-ID: <20120621155911.713748370d898a113e054693@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c: In function 'brcmf_sdio_dump_console':
drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c:3085:3: error: implicit declaration of function 'vzalloc' [-Werror=implicit-function-declaration]
drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c:3085:10: warning: assignment makes pointer from integer without a cast [enabled by default]
drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c:3113:2: error: implicit declaration of function 'vfree' [-Werror=implicit-function-declaration]
Caused by commit 4fc0d0160d59 ("brcmfmac: introduce checkdied debugfs
functionality") from the wireless-next tree. Forgot to include vmalloc.h ?
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-06-21 5:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 5:59 Stephen Rothwell [this message]
2012-06-21 6:04 ` linux-next: build failure after merge of the final tree (wireless-next tree related) Arend van Spriel
2012-06-21 8:59 ` Arend van Spriel
2013-04-04 7:10 Stephen Rothwell
2013-04-04 19:43 ` Larry Finger
2014-03-18 7:41 Stephen Rothwell
2014-03-19 6:20 Stephen Rothwell
2014-03-19 6:23 ` Grumbach, Emmanuel
2014-03-19 19:14 ` John W. Linville
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=20120621155911.713748370d898a113e054693@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arend@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pieterpg@broadcom.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;
as well as URLs for NNTP newsgroup(s).