public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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 17:35:33 +0200	[thread overview]
Message-ID: <YJFpxY6iFHMiPHFE@kroah.com> (raw)
In-Reply-To: <g5YP678olZEf3yQNX2ptK3X6DceFoemqwzEgSJclx_dHFAJfbJBWznYtB74u5g69Onx_6QZkLF-K2muYLa3qsotkPpxbHYuz4Hrs94olZ7c=@protonmail.com>

On Tue, May 04, 2021 at 02:22:51PM +0000, Jari Ruusu wrote:
> On Tuesday, May 4, 2021 4:36 PM, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > On Tue, May 04, 2021 at 01:05:56PM +0000, Jari Ruusu wrote:
> > > 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.
> 
> That patch is in 5.10 + 5.11 + 5.12
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.10.y&id=2a442f11407ec9c9bc9b84d7155484f2b60d01f9
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.11.y&id=a9315228c1d4b1ced803761e81ef761d97f3e2fa
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.12.y&id=f935c64a0c87d86730efd6e1e168555460234d04

{sigh}

It's been a long week, I forgot to update my database of what commit is
in what stable release, my fault.

Can you resend your backports here now, and properly let us know what
kernel they belong into (again, the subject line is very confusing.)

thanks,

greg k-h

  reply	other threads:[~2021-05-04 15:35 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
2021-05-04 14:22               ` Jari Ruusu
2021-05-04 15:35                 ` Greg Kroah-Hartman [this message]
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=YJFpxY6iFHMiPHFE@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox