From: Greg KH <gregkh@linuxfoundation.org>
To: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
aleksandr.loktionov@intel.com, anthony.l.nguyen@intel.com,
jakub.staniszewski@linux.intel.com, pmenzel@molgen.mpg.de,
przemyslaw.kitszel@intel.com, sx.rinitha@intel.com
Subject: Re: Patch "ice: fix retry for AQ command 0x06EE" has been added to the 5.15-stable tree
Date: Tue, 17 Mar 2026 16:39:52 +0100 [thread overview]
Message-ID: <2026031723-graceful-chaos-9ca2@gregkh> (raw)
In-Reply-To: <225eb7e2-c470-4307-90d5-0b56a35c4543@linux.intel.com>
On Tue, Mar 17, 2026 at 04:24:15PM +0100, Dawid Osuchowski wrote:
> On 2026-03-17 4:14 PM, Dawid Osuchowski wrote:
> > On 2026-03-17 1:11 PM, gregkh@linuxfoundation.org wrote:
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.
> > >
> >
> > Hey stable maintainers!
> >
> > This patch **depends heavily** on the change "ice: reintroduce retry
> > mechanism for indirect AQ" which failed to apply for 5.15-stable and
> > 6.1-stable trees.
> >
> > Until I can try to resolve the conflicts and resend, it might be
> > necessary to pull this change from the 5.15-stable and 6.1-stable trees
> > immediately as it will result in multiple WARN messages being printed
> > into the dmesg upon issuing 'ethtool -m' on a interface under the 'ice'
> > driver control.
>
> !!! FALSE ALARM - ABORT !!!
>
> I'm sorry, a bit of a chaotic day here at work...
>
> I was worried the lack of the "ice: reintroduce retry mechanism for indirect
> AQ" patch will result in issues for users. It will not, as my colleague
> Jakub Staniszewski politely informed me that the 5.15-stable and 6.1-stable
> doesn't have the code from Michal Schmidt that we "reverted" using "ice:
> reintroduce retry mechanism for indirect AQ". No warnings will be printed to
> dmesg and everything should work correctly...
>
> Once again I am very sorry
No worries, I'd much rather people warn us and then say "nope, we were
wrong" instead of not saying anything if they think there might be a
problem. So all is good here, thanks!
greg k-h
next prev parent reply other threads:[~2026-03-17 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026031705-nimbly-relatable-1e23@gregkh>
2026-03-17 15:14 ` Patch "ice: fix retry for AQ command 0x06EE" has been added to the 5.15-stable tree Dawid Osuchowski
2026-03-17 15:24 ` Dawid Osuchowski
2026-03-17 15:39 ` Greg KH [this message]
2026-03-17 15:52 ` Dawid Osuchowski
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=2026031723-graceful-chaos-9ca2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=dawid.osuchowski@linux.intel.com \
--cc=jakub.staniszewski@linux.intel.com \
--cc=pmenzel@molgen.mpg.de \
--cc=przemyslaw.kitszel@intel.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sx.rinitha@intel.com \
/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