Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Alexander Wetzel <alexander@wetzel-home.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 5/5] mac80211_hwsim: Ext Key ID support (NATIVE)
Date: Sun, 17 Mar 2019 23:38:23 +0100	[thread overview]
Message-ID: <d4db2ae373172afa8d2eb22e92a54a6f921784b7.camel@sipsolutions.net> (raw)
In-Reply-To: <20190316204208.16497-6-alexander@wetzel-home.de>

Since I'm travelling to netdev and all, I'm not sure I'll actually get
around to this patchset soon.

On Sat, 2019-03-16 at 21:42 +0100, Alexander Wetzel wrote:
> Driver is not supporting hardware encryption and therefore fully
> compatible with Extended Key ID.

On this particular patch now reading this I'm wondering if we shouldn't
just do that in mac80211 if there's no set_key callback? I suspect
that'd affect a few drivers that are otherwise more or less orphaned.

johannes


  reply	other threads:[~2019-03-17 22:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-16 20:42 [PATCH 0/5] Extended Key ID support Alexander Wetzel
2019-03-16 20:42 ` [PATCH 1/5] nl80211/cfg80211: " Alexander Wetzel
2019-03-16 20:42 ` [PATCH 2/5] mac80211: IEEE 802.11 " Alexander Wetzel
2019-03-16 20:42 ` [PATCH 3/5] mac80211: Compatibility " Alexander Wetzel
2019-03-16 20:42 ` [PATCH 4/5] mac80211: Mark A-MPDU keyid borders for drivers Alexander Wetzel
2019-03-16 20:42 ` [PATCH 5/5] mac80211_hwsim: Ext Key ID support (NATIVE) Alexander Wetzel
2019-03-17 22:38   ` Johannes Berg [this message]
2019-03-19 20:44     ` Alexander Wetzel

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=d4db2ae373172afa8d2eb22e92a54a6f921784b7.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=alexander@wetzel-home.de \
    --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