All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: gregory.greenman@intel.com
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 0/9] wifi: iwlwifi: updates intended for v6.2 2022-11-22
Date: Wed, 23 Nov 2022 09:46:46 +0200	[thread overview]
Message-ID: <87wn7mnme1.fsf@kernel.org> (raw)
In-Reply-To: <20221122201040.2618863-1-gregory.greenman@intel.com> (gregory greenman's message of "Tue, 22 Nov 2022 22:10:31 +0200")

gregory.greenman@intel.com writes:

> From: Gregory Greenman <gregory.greenman@intel.com>
>
> Hi,
>
> Here's the third set of patches intended for v6.2, with the fixes.
> Resending all the patches since I think it'll make the review easier.
> The fixes are only for two patches (1 and 4), the rest are unchanged.
>
> It contains EHT adjustments for iwlwifi. It contains only iwlwifi
> changes, all the required mac80211/cfg80211 changes are already merged
> upstream.
>
> As usual, I'm pushing this to a pending branch, for kbuild bot,
> and will send a pull-request later.
>
> Please review.

No need to resend because of this but there's no changelog to list the
changes since v1. Usually we do something like this (I'm making up the
content, I don't know what you actually changed):

v2

* patch 1: fix a typo in the commit log

* patch 5: add missing mutex_unlock() in error handling


-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

      parent reply	other threads:[~2022-11-23  7:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 20:10 [PATCH v2 0/9] wifi: iwlwifi: updates intended for v6.2 2022-11-22 gregory.greenman
2022-11-22 20:10 ` [PATCH v2 1/9] wifi: iwlwifi: mvm: Advertise EHT capabilities gregory.greenman
2022-11-22 20:10 ` [PATCH v2 2/9] wifi: iwlwifi: mvm: support 320 MHz PHY configuration gregory.greenman
2022-11-22 20:10 ` [PATCH v2 3/9] wifi: iwlwifi: rs: add support for parsing max MCS per NSS/BW in 11be gregory.greenman
2022-11-22 20:10 ` [PATCH v2 4/9] wifi: iwlwifi: mvm: add support for EHT 1K aggregation size gregory.greenman
2022-11-22 20:10 ` [PATCH v2 5/9] wifi: iwlwifi: mvm: support PPE Thresholds for EHT gregory.greenman
2022-11-22 20:10 ` [PATCH v2 6/9] wifi: iwlwifi: mvm: set HE PHY bandwidth according to band gregory.greenman
2022-11-22 20:10 ` [PATCH v2 7/9] wifi: iwlwifi: mvm: advertise 320 MHz in 6 GHz only conditionally gregory.greenman
2022-11-22 20:10 ` [PATCH v2 8/9] wifi: iwlwifi: nvm-parse: support A-MPDU in EHT 2.4 GHz gregory.greenman
2022-11-22 20:10 ` [PATCH v2 9/9] wifi: iwlwifi: nvm: Update EHT capabilities for GL device gregory.greenman
2022-11-23  7:46 ` Kalle Valo [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=87wn7mnme1.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=gregory.greenman@intel.com \
    --cc=johannes@sipsolutions.net \
    --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.