From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linux kernel regressions list <regressions@lists.linux.dev>
Subject: AMD Ryzen stutter even despite recent fTPM fix
Date: Sat, 18 Mar 2023 13:20:28 +0100 [thread overview]
Message-ID: <6a7925be-6391-83e3-6af9-849a697698f6@leemhuis.info> (raw)
[TLDR: Just adding a regression reported to bko to the tracking]
Hi, Thorsten here, the Linux kernel's regression tracker. I noticed a
regression reported in bugzilla.kernel.org that seems to be handled
there already, nevertheless I'd like to add to the tracking to ensure
it's doesn't fall through the cracks in the end:
[note: the reporter didn't specify exactly when this started; assuming
6.0..6.2]
#regzbot introduced: v6.0..v6.2
https://bugzilla.kernel.org/show_bug.cgi?id=217212
#regzbot title: AMD Ryzen stutter even despite fTPM fix
#regzbot ignore-activity
See the ticket for details, there were a few replies already.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
reply other threads:[~2023-03-18 12:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6a7925be-6391-83e3-6af9-849a697698f6@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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).