From: Greg KH <gregkh@linuxfoundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@kernel.org>, stable <stable@vger.kernel.org>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Sandipan Das <sandipan.das@amd.com>,
x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/cpu/amd: Fix workaround for erratum 1054
Date: Fri, 18 Apr 2025 14:47:39 +0200 [thread overview]
Message-ID: <2025041819-harsh-outreach-dd6d@gregkh> (raw)
In-Reply-To: <20250418123713.GCaAJHedTC_JWN__Td@fat_crate.local>
On Fri, Apr 18, 2025 at 02:37:13PM +0200, Borislav Petkov wrote:
> On Fri, Apr 18, 2025 at 02:11:44PM +0200, Ingo Molnar wrote:
> > No, it doesn't really 'need' a stable tag, it has a Fixes tag already,
> > which gets processed by the -stable team.
NOOOOOO!!!!
> Last time I asked Greg, he said they scan for those tags but it doesn't hurt
> to Cc stable as it helps.
>
> Greg?
Fixes: is a "best effort if we get around to it because a maintainer
forgot to put an actual cc: stable tag on it".
As the documentation has stated, since the start of the stable kernel
tree work, use a cc: stable tag if you want it to go to a stable tree.
Fixes came years later and we are forced to dig through them
occasionally because people forget. But you do NOT get a FAILED email
if the commit does not apply to a stable tree, and sometimes we just
ignore them entirely if we are busy with other stuff.
So please ALWAYS use cc: stable@ on patches you know you want to be
applied to stable trees. Use the Fixes: tag to tell us how far back to
backport them. That's it. Use both.
thanks,
greg k-h
next prev parent reply other threads:[~2025-04-18 12:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 6:36 [tip: x86/urgent] x86/cpu/amd: Fix workaround for erratum 1054 tip-bot2 for Sandipan Das
2025-04-18 10:40 ` Borislav Petkov
2025-04-18 12:11 ` Ingo Molnar
2025-04-18 12:32 ` Ingo Molnar
2025-04-18 12:37 ` Borislav Petkov
2025-04-18 12:41 ` Ingo Molnar
2025-04-18 12:47 ` Greg KH [this message]
2025-04-18 12:56 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2025-04-18 12:37 tip-bot2 for Sandipan Das
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=2025041819-harsh-outreach-dd6d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sandipan.das@amd.com \
--cc=stable@vger.kernel.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.