From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, bp@alien8.de
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1-stable] x86/CPU/AMD: Properly check the TSA microcode
Date: Sun, 13 Jul 2025 09:06:03 -0400 [thread overview]
Message-ID: <20250712203342-53f56e26abacad80@stable.kernel.org> (raw)
In-Reply-To: <20250711193039.GKaHFmX8215MRwSR_z@fat_crate.local>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Could not find matching upstream commit
No upstream commit was identified. Using temporary commit for testing.
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2025-07-13 13:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 12:03 TSA mitigation doesn't work on 6.6.y Thomas Voegtle
2025-07-11 12:25 ` Borislav Petkov
2025-07-11 13:15 ` Thomas Voegtle
2025-07-11 15:35 ` Borislav Petkov
2025-07-11 16:03 ` Thomas Voegtle
2025-07-11 16:44 ` Borislav Petkov
2025-07-11 16:56 ` Thomas Voegtle
2025-07-11 17:41 ` Borislav Petkov
2025-07-11 18:11 ` Thomas Voegtle
2025-07-11 18:15 ` Borislav Petkov
2025-07-11 19:18 ` [PATCH 6.12-stable] x86/CPU/AMD: Properly check the TSA microcode Borislav Petkov
2025-07-13 13:05 ` Sasha Levin
2025-07-11 19:23 ` [PATCH 6.6-stable] " Borislav Petkov
2025-07-13 13:30 ` Sasha Levin
2025-07-11 19:30 ` [PATCH 6.1-stable] " Borislav Petkov
2025-07-13 13:06 ` Sasha Levin [this message]
2025-07-11 19:45 ` [PATCH 5.15-stable] " Borislav Petkov
2025-07-12 12:04 ` Greg KH
2025-07-13 13:06 ` Sasha Levin
2025-07-13 16:10 ` Borislav Petkov
2025-07-14 1:50 ` Sasha Levin
2025-07-14 10:28 ` Borislav Petkov
2025-07-14 16:30 ` Sasha Levin
2025-07-14 16:33 ` Borislav Petkov
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=20250712203342-53f56e26abacad80@stable.kernel.org \
--to=sashal@kernel.org \
--cc=bp@alien8.de \
--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;
as well as URLs for NNTP newsgroup(s).