From: Jacob Keller <jacob.e.keller@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>,
"Samudrala, Sridhar" <sridhar.samudrala@intel.com>
Cc: "Zaki, Ahmed" <ahmed.zaki@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
"Chittim, Madhu" <madhu.chittim@intel.com>
Subject: Re: Fix Intel's ice driver in stable
Date: Thu, 16 May 2024 10:08:54 -0700 [thread overview]
Message-ID: <9e8e781a-da18-4f9f-9d55-ec2f46951286@intel.com> (raw)
In-Reply-To: <2024051655-manned-aviation-fa48@gregkh>
On 5/15/2024 10:46 PM, Greg KH wrote:
> On Thu, May 16, 2024 at 05:12:40AM +0000, Samudrala, Sridhar wrote:
>> We need to fix this ASAP. Flipkart reported this issue with 6.1.x stable kernel.
>> Not sure why this commit was backported to LTS kernel as it is not a bug fix, but introduced as part of enabling live migration.
>
> Back in March you were notified this was going to be picked up for the
> stable tree as part of the AUTOSEL work:
> https://lore.kernel.org/r/20240329122652.3082296-63-sashal@kernel.org
>
> Any reason this wasn't noticed then?
>
> thanks,
>
> greg k-h
I saw this patch go by but didn't notice that the other two weren't
selected. The patches were sent as a series and tested as a series. The
dependency on the other changes was likely not noticed.
next prev parent reply other threads:[~2024-05-16 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 21:16 Fix Intel's ice driver in stable Ahmed Zaki
2024-05-16 5:12 ` Samudrala, Sridhar
2024-05-16 5:46 ` Greg KH
2024-05-16 17:08 ` Jacob Keller [this message]
2024-05-16 6:44 ` Greg KH
2024-05-16 17:10 ` Jacob Keller
2024-05-22 15:44 ` Greg KH
2024-05-22 20:28 ` 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=9e8e781a-da18-4f9f-9d55-ec2f46951286@intel.com \
--to=jacob.e.keller@intel.com \
--cc=ahmed.zaki@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=madhu.chittim@intel.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sridhar.samudrala@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