From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
"John W. Linville" <linville@tuxdriver•com>
Cc: "linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>
Subject: RE: linux-next: build failure after merge of the final tree (wireless-next tree related)
Date: Wed, 19 Mar 2014 06:23:55 +0000 [thread overview]
Message-ID: <0BA3FCBA62E2DC44AF3030971E174FB303DB4940@HASMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20140319172035.b4e7c4043b486d8eeaa0534a@canb.auug.org.au>
>
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc allyesconfig)
> failed like this:
>
> drivers/net/wireless/iwlwifi/mvm/debugfs.c: In function
> 'iwl_dbgfs_fw_error_dump_release':
> drivers/net/wireless/iwlwifi/mvm/debugfs.c:161:2: error: implicit declaration
> of function 'vfree' [-Werror=implicit-function-declaration]
> vfree(file->private_data);
> ^
Sorry for that - patch on the way.
>
> Caused by commit 1bd3cbc1a0e9 ("iwlwifi: mvm: send udev event upon
> firmware error to dump logs") from the wireless-next tree. See Rule 1
> from Documentation/SubmitChecklist.
>
> I have reverted that commit (and commit cdb00563fe2c ("iwlwifi: mvm: BT
> Coex - add debugfs hook to set BT Tx priority") that may depend on it)
> for today.
> --
> Cheers,
> Stephen Rothwell sfr@canb•auug.org.au
next prev parent reply other threads:[~2014-03-19 6:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 6:20 linux-next: build failure after merge of the final tree (wireless-next tree related) Stephen Rothwell
2014-03-19 6:23 ` Grumbach, Emmanuel [this message]
2014-03-19 19:14 ` John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2014-03-18 7:41 Stephen Rothwell
2013-04-04 7:10 Stephen Rothwell
2013-04-04 19:43 ` Larry Finger
2012-06-21 5:59 Stephen Rothwell
2012-06-21 6:04 ` Arend van Spriel
2012-06-21 8:59 ` Arend van Spriel
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=0BA3FCBA62E2DC44AF3030971E174FB303DB4940@HASMSX103.ger.corp.intel.com \
--to=emmanuel.grumbach@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linville@tuxdriver$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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