From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes.berg@intel.com>,
<ath6kl@lists.infradead.org>
Subject: Re: [PATCH 2/2] cfg80211: allow passing frame type to cfg80211_inform_bss()
Date: Thu, 14 Aug 2014 11:57:00 +0300 [thread overview]
Message-ID: <8761hvo3dv.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1407870219-1720-2-git-send-email-johannes@sipsolutions.net> (Johannes Berg's message of "Tue, 12 Aug 2014 21:03:39 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> From: Johannes Berg <johannes.berg@intel.com>
>
> When using the cfg80211_inform_bss[_width]() functions drivers
> cannot currently indicate whether the data was received in a
> beacon or probe response. Fix that by passing a new enum that
> indicates such (or unknown).
>
> For good measure, use it in ath6kl.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> drivers/net/wireless/ath/ath6kl/cfg80211.c | 1 +
> drivers/net/wireless/ath/ath6kl/wmi.c | 43 +++++-----------------
Thanks. For the ath6kl part:
Acked-by: Kalle Valo <kvalo@qca.qualcomm.com>
--
Kalle Valo
next prev parent reply other threads:[~2014-08-14 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 19:03 [PATCH 1/2] cfg80211: clarify BSS probe response vs. beacon data Johannes Berg
2014-08-12 19:03 ` [PATCH 2/2] cfg80211: allow passing frame type to cfg80211_inform_bss() Johannes Berg
2014-08-14 8:57 ` Kalle Valo [this message]
2014-08-14 9:23 ` Arend van Spriel
2014-08-13 10:57 ` [PATCH 1/2] cfg80211: clarify BSS probe response vs. beacon data Eliad Peller
2014-08-13 11:08 ` Johannes Berg
2014-08-13 11:13 ` Eliad Peller
2014-08-13 11:20 ` Johannes Berg
2014-08-13 11:39 ` Eliad Peller
2014-08-13 11:46 ` Johannes Berg
2014-08-13 11:57 ` Eliad Peller
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=8761hvo3dv.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl@lists.infradead.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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).