linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH 0/2] more crypto access for drivers
Date: Thu, 07 Jul 2011 18:57:59 +0200	[thread overview]
Message-ID: <20110707165759.856063840@sipsolutions.net> (raw)

With the TID 0 vs. non-QoS issue out of the way
I'm happy with these now. Will need additional
code (separate patch) for keeping the connection
up (and safe) after resume, but I'm not there
yet. For now this allows me to keep the it up
and safe into suspend with GTK rekey in the
device.

johannes


             reply	other threads:[~2011-07-07 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 16:57 Johannes Berg [this message]
2011-07-07 16:58 ` [PATCH 1/2] mac80211: allow drivers to access key sequence counter Johannes Berg
2011-07-07 16:58 ` [PATCH 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=20110707165759.856063840@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).