From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [RFC 1/2] mac80211: allow drivers to access key sequence counter
Date: Wed, 06 Jul 2011 16:33:21 +0200 [thread overview]
Message-ID: <1309962801.3893.9.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20110706121315.215752759@sipsolutions.net> (sfid-20110706_141342_555231_9BAC1052)
On Wed, 2011-07-06 at 14:12 +0200, Johannes Berg wrote:
> +/**
> + * ieee80211_get_key_rx_seq - get key RX sequence counter
> + *
> + * @keyconf: the parameter passed with the set key
> + * @tid: the TID, or -1 for the non-QoS value
This is of course wrong. The -1 should be for *management* frames. I'll
fix that for the real submission.
johannes
next prev parent reply other threads:[~2011-07-06 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 12:12 [RFC 0/2] more crypto access for drivers Johannes Berg
2011-07-06 12:12 ` [RFC 1/2] mac80211: allow drivers to access key sequence counter Johannes Berg
2011-07-06 14:33 ` Johannes Berg [this message]
2011-07-06 12:12 ` [RFC 2/2] mac80211: allow driver to generate P1K for IV32 Johannes Berg
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=1309962801.3893.9.camel@jlt3.sipsolutions.net \
--to=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).