From: "Arend van Spriel" <arend@broadcom.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Pieter-Paul Giesberts <pieterpg@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>
Subject: Re: linux-next: build failure after merge of the final tree (wireless-next tree related)
Date: Thu, 21 Jun 2012 10:59:52 +0200 [thread overview]
Message-ID: <4FE2E288.2000201@broadcom.com> (raw)
In-Reply-To: <20120621155911.713748370d898a113e054693@canb.auug.org.au>
On 06/21/2012 07:59 AM, Stephen Rothwell wrote:
> 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.
Hi Stephen,
We have setup a mailing list brcm80211-dev-list@broadcom.com for
reporting driver issues to make sure the right people are informed
regardless organizational changes. Feel free to use that as needed.
Gr. AvS
next prev parent reply other threads:[~2012-06-21 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 5:59 linux-next: build failure after merge of the final tree (wireless-next tree related) Stephen Rothwell
2012-06-21 6:04 ` Arend van Spriel
2012-06-21 8:59 ` Arend van Spriel [this message]
-- strict thread matches above, loose matches on Subject: below --
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=4FE2E288.2000201@broadcom.com \
--to=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 \
--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 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).