From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Pandiyarajan Pitchaimuthu <c_ppitch@qti.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qca.qualcomm.com>
Subject: Re: [PATCH] ath6kl: Blocked client notification
Date: Fri, 12 Oct 2012 15:19:46 +0300 [thread overview]
Message-ID: <50780AE2.5020506@qca.qualcomm.com> (raw)
In-Reply-To: <1348220333-5466-1-git-send-email-c_ppitch@qca.qualcomm.com>
On 09/21/2012 12:38 PM, Pandiyarajan Pitchaimuthu wrote:
> When a station tries to connect to an AP and if the MAC of the
> station is in the AP's block list, the station cannot connect to the
> AP. This is notified to the userspace with event
> NL80211_CMD_CONN_FAILED and attribute NL80211_ATTR_CONN_FAILED_REASON.
> The reason sent will be NL80211_CONN_FAIL_BLOCKED_CLIENT.
>
> Signed-off-by: Pandiyarajan Pitchaimuthu <c_ppitch@qca.qualcomm.com>
Thanks, applied.
Kalle
prev parent reply other threads:[~2012-10-12 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 9:38 [PATCH] ath6kl: Blocked client notification Pandiyarajan Pitchaimuthu
2012-10-12 12:19 ` Kalle Valo [this message]
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=50780AE2.5020506@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qca.qualcomm.com \
--cc=c_ppitch@qti.qualcomm.com \
--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).