public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@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: Sat, 01 May 2021 10:12:42 +0300	[thread overview]
Message-ID: <608CFF6A.4BC054A3@users.sourceforge.net> (raw)
In-Reply-To: 20210430141910.521897363@linuxfoundation.org

Greg Kroah-Hartman wrote:
> From: Jiri Kosina <jkosina@suse.cz>
> 
> commit e7020bb068d8be50a92f48e36b236a1a1ef9282e upstream.
> 
> Analogically to what we did in 2800aadc18a6 ("iwlwifi: Fix softirq/hardirq
> disabling in iwl_pcie_enqueue_hcmd()"), we must apply the same fix to
> iwl_pcie_gen2_enqueue_hcmd(), as it's being called from exactly the same
> contexts.

Greg,
This patch and above mentioned earlier patch
"iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()",
upstream commit 2800aadc18a64c96b051bcb7da8a7df7d505db3f, both need
to be backported to older kernels too.

I see that there are trivial context rejects if/when you attempt to
apply those patches to older kernels. Those trivial context rejects
should not prevent backporting them. Maybe run both patches through sed?

sed -e s/iwl_txq_space/iwl_queue_space/ -e s/iwl_txq_get_/iwl_pcie_get_/

My ability test in-tree iwlwifi is limited. I compile out-of-tree
iwlwifi source, and testing that is limited to pinging mobile-wifi
router that does not have SIM-card.

-- 
Jari Ruusu  4096R/8132F189 12D6 4C3A DCDA 0AA4 27BD  ACDF F073 3C80 8132 F189

  reply	other threads:[~2021-05-01  7:28 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 [this message]
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
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=608CFF6A.4BC054A3@users.sourceforge.net \
    --to=jariruusu@users.sourceforge.net \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox