From: Johannes Berg <johannes@sipsolutions.net>
To: Cedric Izoard <Cedric.Izoard@ceva-dsp.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3] mac80211: Get IV len from key conf and not cipher scheme
Date: Tue, 17 Mar 2015 11:02:13 +0100 [thread overview]
Message-ID: <1426586533.1985.3.camel@sipsolutions.net> (raw)
In-Reply-To: <5842EA9CC042B141995329508713AD672105AD37@ILMAIL1.corp.local>
On Wed, 2015-03-11 at 16:29 +0000, Cedric Izoard wrote:
> When a key is installed using a cipher scheme, a new flag
> IEE80211_KEY_FLAG_CIPHER_SCHEME is set.
Should this flag really be visible to the driver? The driver should
better know if it's a CS key anyway, no? And then we could use an
internal key flag (see net/mac80211/key.h) and avoid increasing the size
of the flags field.
johannes
prev parent reply other threads:[~2015-03-17 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 16:29 [PATCH v3] mac80211: Get IV len from key conf and not cipher scheme Cedric Izoard
2015-03-12 8:08 ` Stepanov, Max
2015-03-17 10:02 ` Johannes Berg [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=1426586533.1985.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Cedric.Izoard@ceva-dsp.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).