From: Kalle Valo <kvalo@qca.qualcomm.com>
To: kbuild test robot <lkp@intel.com>
Cc: <c_traja@qti.qualcomm.com>,
Manikanta pubbisetty <c_mpubbi@qti.qualcomm.com>,
<linux-wireless@vger.kernel.org>, <ath10k@lists.infradead.org>,
<kbuild-all@01.org>, <johannes@sipsolutions.net>
Subject: Re: [PATCH 2/2] ath10k: set peer MFP flag in peer assoc command
Date: Wed, 7 Oct 2015 11:22:08 +0300 [thread overview]
Message-ID: <87612j1427.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <201510071317.0ndTjHKZ%fengguang.wu@intel.com> (kbuild test robot's message of "Wed, 7 Oct 2015 13:34:39 +0800")
kbuild test robot <lkp@intel.com> writes:
> Hi Tamizh,
>
> [auto build test ERROR on next-20151006 -- if it's inappropriate base, please ignore]
>
> config: xtensa-allyesconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=xtensa
>
> All errors (new ones prefixed by >>):
>
> drivers/net/wireless/ath/ath10k/mac.c: In function 'ath10k_peer_assoc_h_crypto':
>>> drivers/net/wireless/ath/ath10k/mac.c:2014:9: error: 'struct ieee80211_sta' has no member named 'mfp'
> if (sta->mfp &&
This is expected as the patch depends on not yet commited patch 'Revert
"mac80211: remove exposing 'mfp' to drivers"'.
--
Kalle Valo
next prev parent reply other threads:[~2015-10-07 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 5:16 [PATCH 2/2] ath10k: set peer MFP flag in peer assoc command c_traja
2015-10-07 5:34 ` kbuild test robot
2015-10-07 8:22 ` Kalle Valo [this message]
2015-10-07 8:59 ` Raja, Tamizh Chelvam
2015-10-31 9:38 ` Kalle Valo
2015-11-04 5:20 ` Raja, Tamizh Chelvam
2015-11-04 7:57 ` Kalle Valo
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=87612j1427.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=c_mpubbi@qti.qualcomm.com \
--cc=c_traja@qti.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=kbuild-all@01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.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).