From: Johannes Berg <johannes@sipsolutions.net>
To: Ravi Sharma <sharmaravi.lx@gmail.com>
Cc: "Divinsky, Yonatan" <yoni.divinsky@ti.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: add op to configure default key id to driver
Date: Thu, 17 May 2012 13:05:22 +0200 [thread overview]
Message-ID: <1337252722.4332.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAEZZmbF6wa3JF48KsCiyg4T7OsBS73OnzAMVYPkPdPro9EYUtg@mail.gmail.com> (sfid-20120517_103653_559210_BF230AEA)
On Thu, 2012-05-17 at 14:06 +0530, Ravi Sharma wrote:
> Hi All
> I know this use case is quite trivial looking regarding WEP (Since it
> is going to be deprecated), we faced a issue with minap (softap) in
> WEP security with auth mode as shared. Since the default key is not
> passed to driver, we can not program firmware default key idx (default
> key is programmed when data packet exchange started, looking into type
> of encryption) and the handshake failed in shared auth mode. In open
> mode, there is no need for this.
Now you're talking about something else entirely? What does this have to
do with auto-ARP responses??
Can we get that story straight? :-) And then a patch that actually
explains & documents it ... Remember that the changelog should indicate
why you're changing something.
johannes
next prev parent reply other threads:[~2012-05-17 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 12:18 [PATCH] mac80211: add op to configure default key id to driver Yoni Divinsky
2012-05-08 14:06 ` Johannes Berg
[not found] ` <CANJm+iAoVkPOO61ufrM3mxzsURFZzuNcMm9N6Y=3xUbSCaC1+w@mail.gmail.com>
[not found] ` <1337072920.4546.0.camel@jlt3.sipsolutions.net>
[not found] ` <CANJm+iDif1+KREB=CJ_wYbo+Hzxo=nJL6fUxbBTQ5_C8Tz0E9Q@mail.gmail.com>
2012-05-17 8:25 ` Fwd: " Divinsky, Yonatan
[not found] ` <CAEZZmbEExFr6=7G6kQb_bbpt=wfiNDuoR+U4_Eu_wLdair=SrA@mail.gmail.com>
2012-05-17 8:36 ` Ravi Sharma
2012-05-17 11:05 ` Johannes Berg [this message]
2012-05-18 5:59 ` Ravi Sharma
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=1337252722.4332.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sharmaravi.lx@gmail.com \
--cc=yoni.divinsky@ti.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