From: Alejandro Colomar <alx@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Jeff Johnson" <jeff.johnson@oss.qualcomm.com>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
linux-wireless@vger.kernel.org,
"Rajkumar Manoharan" <rmanohar@qti.qualcomm.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH v1] wifi: ath9k: Fix typo
Date: Tue, 24 Feb 2026 23:52:45 +0100 [thread overview]
Message-ID: <aZ4rgNrA7RS0OuoB@devuan> (raw)
In-Reply-To: <2026022405-mundane-caucus-6aa9@gregkh>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
Hi Greg,
On 2026-02-24T13:37:09-0800, Greg KH wrote:
> > [Do not backport to stable]
> > Fixes: ...
>
> As per the in-kernel documentation file
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>
> There furthermore is a variant of the stable tag you can use to make the stable
> team's backporting tools (e.g AUTOSEL or scripts that look for commits
> containing a 'Fixes:' tag) ignore a change::
>
> Cc: <stable+noautosel@kernel.org> # reason goes here, and must be present
>
> So I think it is documented already :)
Thanks! I'll use that. :)
Cheers,
Alex
>
> thanks,
>
> greg k-h
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-24 22:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 22:25 [PATCH v1] wifi: ath9k: Fix typo Alejandro Colomar
2026-02-23 15:17 ` Toke Høiland-Jørgensen
2026-02-24 18:45 ` Jeff Johnson
2026-02-24 21:27 ` Alejandro Colomar
2026-02-24 21:34 ` Jeff Johnson
2026-02-24 22:55 ` Alejandro Colomar
2026-02-24 23:07 ` Jeff Johnson
2026-02-24 23:09 ` Jeff Johnson
2026-02-24 23:23 ` Alejandro Colomar
2026-02-25 0:04 ` Jeff Johnson
2026-02-25 0:10 ` Alejandro Colomar
2026-02-24 21:37 ` Greg KH
2026-02-24 22:52 ` Alejandro Colomar [this message]
2026-02-26 21:29 ` Jeff Johnson
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=aZ4rgNrA7RS0OuoB@devuan \
--to=alx@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rmanohar@qti.qualcomm.com \
--cc=toke@toke.dk \
/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