From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jari Ruusu <jariruusu@protonmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>, Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [PATCH 5.10 1/2] iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_gen2_enqueue_hcmd()
Date: Tue, 4 May 2021 15:36:08 +0200 [thread overview]
Message-ID: <YJFNyOGrF8RcTTlc@kroah.com> (raw)
In-Reply-To: <npSsinT79DB6Ze8QTkmLcuOTyVwRcy2FbOf0tDjpEHbTxKdYmLar8Br66_ypLjzZ86sIJKnSbUHeehagPR6RqxsJsKdWW_vWnXOUEhMC14g=@protonmail.com>
On Tue, May 04, 2021 at 01:05:56PM +0000, Jari Ruusu wrote:
> On Tuesday, May 4, 2021 10:24 AM, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > All now queued up, thanks.
>
> For 5.4 and 4.19 and 4.14 kernels there were 2 patches,
> first patch is upstream commit 2800aadc18a64c96b051bcb7da8a7df7d505db3f,
That one is queued up, thanks.
> second patch is upstream commit e7020bb068d8be50a92f48e36b236a1a1ef9282e.
This is not in any newer stable trees, and it was not obvious what you
were doing here at all.
> First patch modifies iwlwifi/pcie/tx.c (older models use this)
> Second patch modifies iwlwifi/pcie/tx-gen2.c (for newer models)
>
> I see you queued only the "tx.c" patches, not the "tx-gen2.c" ones.
That is because it is not in 5.12.y yet either, right?
If it needs to be there, please let us know. Having a subject line that
said "5.10" for all of these was impossible to determine...
So, for e7020bb068d8 ("iwlwifi: Fix softirq/hardirq disabling in
iwl_pcie_gen2_enqueue_hcmd()") what tree(s) do you need it in exactly?
thanks,
greg k-h
next prev parent reply other threads:[~2021-05-04 13:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 14:20 [PATCH 5.10 0/2] 5.10.34-rc1 review Greg Kroah-Hartman
2021-04-30 14:20 ` [PATCH 5.10 1/2] iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_gen2_enqueue_hcmd() Greg Kroah-Hartman
2021-05-01 7:12 ` Jari Ruusu
2021-05-02 11:03 ` Greg Kroah-Hartman
2021-05-03 11:20 ` Jari Ruusu
2021-05-03 11:22 ` Jari Ruusu
2021-05-03 11:23 ` Jari Ruusu
2021-05-03 11:24 ` Jari Ruusu
2021-05-03 11:25 ` Jari Ruusu
2021-05-03 11:27 ` Jari Ruusu
2021-05-04 7:24 ` Greg Kroah-Hartman
2021-05-04 13:05 ` Jari Ruusu
2021-05-04 13:36 ` Greg Kroah-Hartman [this message]
2021-05-04 14:22 ` Jari Ruusu
2021-05-04 15:35 ` Greg Kroah-Hartman
2021-05-04 17:02 ` Jari Ruusu
2021-05-04 17:18 ` Greg Kroah-Hartman
2021-05-04 17:04 ` Jari Ruusu
2021-04-30 14:20 ` [PATCH 5.10 2/2] mei: me: add Alder Lake P device id Greg Kroah-Hartman
2021-04-30 17:35 ` [PATCH 5.10 0/2] 5.10.34-rc1 review Fox Chen
2021-04-30 18:11 ` Jon Hunter
2021-04-30 20:14 ` Pavel Machek
2021-04-30 22:35 ` Sudip Mukherjee
2021-04-30 23:29 ` Florian Fainelli
2021-05-01 7:45 ` Naresh Kamboju
2021-05-01 13:13 ` Guenter Roeck
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=YJFNyOGrF8RcTTlc@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jariruusu@protonmail.com \
--cc=jkosina@suse.cz \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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.