public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: stable@vger.kernel.org, Brett Creeley <brett.creeley@intel.com>,
	Konrad Jankowski <konrad0.jankowski@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>
Subject: Re: [PATCH 1/2] ice: Fix race conditions between virtchnl handling and VF ndo ops
Date: Mon, 28 Feb 2022 12:23:55 +0100	[thread overview]
Message-ID: <Yhywy/LYW38Aavxt@kroah.com> (raw)
In-Reply-To: <YhytnJGxStO0Gai9@kroah.com>

On Mon, Feb 28, 2022 at 12:10:20PM +0100, Greg KH wrote:
> On Fri, Feb 25, 2022 at 12:21:00PM -0800, Jacob Keller wrote:
> > From: Brett Creeley <brett.creeley@intel.com>
> > 
> > commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d upstream.
> > 
> > [I had to fix the cherry-pick manually as the patch added a line around
> > some context that was missing.]
> 
> What stable tree(s) is this for?$

Looks like it applied only to 5.15.y.  Can you also provide backports
for the other older kernels that these are needed for?

thanks,

greg k-h

  reply	other threads:[~2022-02-28 11:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 20:21 [PATCH 1/2] ice: Fix race conditions between virtchnl handling and VF ndo ops Jacob Keller
2022-02-25 20:21 ` [PATCH 2/2] ice: fix concurrent reset and removal of VFs Jacob Keller
2022-02-28 11:10 ` [PATCH 1/2] ice: Fix race conditions between virtchnl handling and VF ndo ops Greg KH
2022-02-28 11:23   ` Greg KH [this message]
2022-02-28 19:13     ` Keller, Jacob E
2022-02-28 20:57     ` Keller, Jacob E
2022-03-05 13:43       ` Greg KH
2022-03-07 18:38         ` Keller, Jacob E
2022-02-28 19:13   ` Keller, Jacob E
  -- strict thread matches above, loose matches on Subject: below --
2022-02-28 20:46 Jacob Keller
2022-03-05 13:40 ` Greg KH
2022-03-07 18:38   ` Keller, Jacob E

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=Yhywy/LYW38Aavxt@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=brett.creeley@intel.com \
    --cc=jacob.e.keller@intel.com \
    --cc=konrad0.jankowski@intel.com \
    --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