All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Emmanuel Grumbach <egrumbach@gmail.com>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Eliad Peller <eliad@wizery.com>,
	Eliad Peller <eliadx.peller@intel.com>
Subject: Re: [PATCH 2/3] iwlwifi: mvm: move TX PN assignment for TKIP to the driver
Date: Sun, 14 Feb 2016 20:24:35 +0100	[thread overview]
Message-ID: <1455477875.2564.0.camel@sipsolutions.net> (raw)
In-Reply-To: <CANUX_P3Ybzowsf3Kg7TFhtpq+H4bDWMswrGHhkrvHKtnZaEVhA@mail.gmail.com> (sfid-20160214_183403_853776_9F1FCA58)

On Sun, 2016-02-14 at 19:34 +0200, Emmanuel Grumbach wrote:
> 
> Since the 3rd patch needs to be dropped anyway, let's route this one
> through my tree as usual.

It doesn't really have to be dropped, why? We can just make the same
adjustment as for dvm in the patch.

johannes

  reply	other threads:[~2016-02-14 19:24 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 [this message]
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
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=1455477875.2564.0.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.