From: Johannes Berg <johannes@sipsolutions.net>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
Eliad Peller <eliad@wizery.com>
Cc: Emmanuel Grumbach <egrumbach@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Peller, EliadX" <eliadx.peller@intel.com>
Subject: Re: [PATCH 2/3] iwlwifi: mvm: move TX PN assignment for TKIP to the driver
Date: Mon, 15 Feb 2016 11:14:33 +0100 [thread overview]
Message-ID: <1455531273.5210.2.camel@sipsolutions.net> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB32EA1338D@hasmsx107.ger.corp.intel.com>
On Mon, 2016-02-15 at 09:24 +0000, Grumbach, Emmanuel wrote:
>
> It doesn't feel right to remove this function in mac80211-next.git
> and
> touch 3 drivers along the way, but I don't mind. Johannes, what do
> you say?
I don't see any problem with that? I've touched far more drivers (like
"every single one") when doing API updates :)
johannes
next prev parent reply other threads:[~2016-02-15 10:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 11:56 [PATCH 1/3] mac80211: move TKIP TX IVs to public part of key struct Emmanuel Grumbach
2016-02-14 11:56 ` [PATCH 2/3] iwlwifi: mvm: move TX PN assignment for TKIP to the driver Emmanuel Grumbach
2016-02-14 17:34 ` Emmanuel Grumbach
2016-02-14 19:24 ` Johannes Berg
2016-02-14 19:37 ` Grumbach, Emmanuel
2016-02-15 9:06 ` Eliad Peller
2016-02-15 9:16 ` Grumbach, Emmanuel
2016-02-15 9:19 ` Eliad Peller
2016-02-15 9:24 ` Grumbach, Emmanuel
2016-02-15 10:14 ` Johannes Berg [this message]
2016-02-14 11:56 ` [PATCH 3/3] mac80211: remove ieee80211_get_key_tx_seq/ieee80211_set_key_tx_seq Emmanuel Grumbach
2016-02-14 13:03 ` kbuild test robot
2016-02-14 14:00 ` kbuild test robot
2016-02-23 10:07 ` [PATCH 1/3] mac80211: move TKIP TX IVs to public part of key struct 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=1455531273.5210.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=egrumbach@gmail.com \
--cc=eliad@wizery.com \
--cc=eliadx.peller@intel.com \
--cc=emmanuel.grumbach@intel.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).