linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Greenman, Gregory" <gregory.greenman@intel.com>
To: "kvalo@kernel.org" <kvalo@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>
Subject: Re: [PATCH 00/10] iwlwifi: updates intended for v5.18 2022-05-17
Date: Tue, 17 May 2022 09:38:07 +0000	[thread overview]
Message-ID: <ac00ab264de1d3d615c956ec256caf9ff30d1206.camel@intel.com> (raw)
In-Reply-To: <20220517090514.211796-1-gregory.greenman@intel.com>

On Tue, 2022-05-17 at 12:05 +0300, gregory.greenman@intel.com wrote:
> From: Gregory Greenman <gregory.greenman@intel.com>
> 
> Hello,
> 
> Here's a set of patches intended for v5.18 if time permits. It's the
> usual developement, bugfixes and small cleanups. Nothing major in
> this
> series.
> 
> Thanks,
> Gregory
> 
> Avraham Stern (1):
>   iwlwifi: mei: clear the sap data header before sending
> 
> Emmanuel Grumbach (2):
>   iwlwifi: mvm: fix assert 1F04 upon reconfig
>   iwlwifi: mvm: always tell the firmware to accept MCAST frames in
> BSS
> 
> Haim Dreyfuss (1):
>   iwlwifi: mvm: use NULL instead of ERR_PTR when parsing wowlan
> status
> 
> Johannes Berg (4):
>   iwlwifi: pcie: simplify MSI-X cause mapping
>   iwlwifi: mvm: clean up authorized condition
>   iwlwifi: fw: init SAR GEO table only if data is present
>   iwlwifi: mei: fix potential NULL-ptr deref
> 
> Miri Korenblit (1):
>   iwlwifi: mvm: remove vif_count
> 
> Mordechay Goodstein (1):
>   iwlwifi: mvm: add OTP info in case of init failure
> 
>  drivers/net/wireless/intel/iwlwifi/fw/acpi.c  |  3 ++
>  drivers/net/wireless/intel/iwlwifi/iwl-prph.h |  2 +
>  drivers/net/wireless/intel/iwlwifi/mei/main.c |  3 ++
>  drivers/net/wireless/intel/iwlwifi/mvm/d3.c   | 22 ++++-----
>  drivers/net/wireless/intel/iwlwifi/mvm/fw.c   | 15 +++---
>  .../net/wireless/intel/iwlwifi/mvm/mac-ctxt.c | 32 +++----------
>  .../net/wireless/intel/iwlwifi/mvm/mac80211.c | 17 ++-----
>  drivers/net/wireless/intel/iwlwifi/mvm/mvm.h  |  1 -
>  .../net/wireless/intel/iwlwifi/mvm/power.c    |  3 ++
>  drivers/net/wireless/intel/iwlwifi/mvm/rx.c   | 44 ++++++++++++-----
>  .../net/wireless/intel/iwlwifi/pcie/trans.c   | 48 +++++++++++------
> --
>  11 files changed, 102 insertions(+), 88 deletions(-)
> 
Considering the timeline, v5.19 seems like a more feasible option.
So, let's use it for v5.19.
Thanks!
Gregory

      parent reply	other threads:[~2022-05-17  9:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17  9:05 [PATCH 00/10] iwlwifi: updates intended for v5.18 2022-05-17 gregory.greenman
2022-05-17  9:05 ` [PATCH 01/10] iwlwifi: pcie: simplify MSI-X cause mapping gregory.greenman
2022-05-17  9:05 ` [PATCH 02/10] iwlwifi: mvm: use NULL instead of ERR_PTR when parsing wowlan status gregory.greenman
2022-05-17  9:05 ` [PATCH 03/10] iwlwifi: mvm: clean up authorized condition gregory.greenman
2022-05-17  9:05 ` [PATCH 04/10] iwlwifi: fw: init SAR GEO table only if data is present gregory.greenman
2022-05-17  9:05 ` [PATCH 05/10] iwlwifi: mvm: fix assert 1F04 upon reconfig gregory.greenman
2022-05-17  9:05 ` [PATCH 06/10] iwlwifi: mvm: add OTP info in case of init failure gregory.greenman
2022-05-17  9:05 ` [PATCH 07/10] iwlwifi: mvm: always tell the firmware to accept MCAST frames in BSS gregory.greenman
2022-05-17  9:05 ` [PATCH 08/10] iwlwifi: mvm: remove vif_count gregory.greenman
2022-05-17  9:05 ` [PATCH 09/10] iwlwifi: mei: clear the sap data header before sending gregory.greenman
2022-05-17  9:05 ` [PATCH 10/10] iwlwifi: mei: fix potential NULL-ptr deref gregory.greenman
2022-05-17  9:38 ` Greenman, Gregory [this message]

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=ac00ab264de1d3d615c956ec256caf9ff30d1206.camel@intel.com \
    --to=gregory.greenman@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --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).