From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: stable@vger.kernel.org
Cc: stable-commits@vger.kernel.org, gregkh@linuxfoundation.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 6.1-stable tree
Date: Tue, 17 Mar 2026 16:17:28 +0100 [thread overview]
Message-ID: <e9720578-7922-40c0-8c18-d2856180a884@linux.intel.com> (raw)
In-Reply-To: <2026031719-kiwi-anagram-b69c@gregkh>
On 2026-03-17 1:11 PM, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> ice: fix retry for AQ command 0x06EE
>
> to the 6.1-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> ice-fix-retry-for-aq-command-0x06ee.patch
> and it can be found in the queue-6.1 subdirectory.
>
> 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 6.1-stable and
5.15-stable trees.
Until I can try to resolve the conflicts and resend, it might be
necessary to pull this change from the 6.1-stable and 5.15-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.
What is the timeline is for resending a conflict free version of the
"ice: reintroduce retry mechanism for indirect AQ" patch for 6.1-stable
and 5.15-stable? And ensuring that the "ice: reintroduce retry mechanism
for indirect AQ" commit lands in the tree before "ice: fix retry for AQ
command 0x06EE"?
I don't know how to make that requirement / relation between commits
known for stable. I didn't find anything in the docs and I assumed if
the whole series doesn't get applied to a given tree (e.g. 6.1-stable
and 5.15-stable as is the case here) then the rest also doesn't. If
there's a way to hint at that for future submissions, please share the
relevant doc / guideline. Sorry!
Best regards
Dawid
parent reply other threads:[~2026-03-17 15:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2026031719-kiwi-anagram-b69c@gregkh>]
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=e9720578-7922-40c0-8c18-d2856180a884@linux.intel.com \
--to=dawid.osuchowski@linux.intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=gregkh@linuxfoundation.org \
--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