All of
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)" <>
To: Jarkko Sakkinen <>,
	Linux regressions mailing list <>
Cc: Linus Torvalds <>,
	Peter Huewe <>, Jason Gunthorpe <>,
	Dominik Brodowski <>,
	Herbert Xu <>,,
	James Bottomley <>,, Bell <>,
	"Jason A . Donenfeld" <>,,,
	Mario Limonciello <>
Subject: Re: [PATCH v3] tpm: disable hwrng for fTPM on some AMD designs
Date: Sun, 12 Mar 2023 11:40:36 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <ZA0t/>

On 12.03.23 02:42, Jarkko Sakkinen wrote:
> On Sun, Mar 12, 2023 at 03:35:08AM +0200, Jarkko Sakkinen wrote:
>> On Fri, Mar 10, 2023 at 06:43:47PM +0100, Thorsten Leemhuis wrote:
>>> [adding Linux to the list of recipients]
>>> On 08.03.23 10:42, Linux regression tracking (Thorsten Leemhuis) wrote:
>>>> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
>>>> for once, to make this easily accessible to everyone.
>>>> Jarkko, thx for reviewing and picking below fix up. Are you planning to
>>>> send this to Linus anytime soon, now that the patch was a few days in
>>>> next? It would be good to get this 6.1 regression finally fixed, it
>>>> already took way longer then the time frame
>>>> Documentation/process/handling-regressions.rst outlines for a case like
>>>> this. But well, that's how it is sometimes...
>>> Linus, would you consider picking this fix up directly from here or from
>>> linux-next (8699d5244e37)? It's been in the latter for 9 days now
>>> afaics. And the issue seems to bug more than just one or two users, so
>>> it IMHO would be good to get this finally resolved.
>>> Jarkko didn't reply to my inquiry, guess something else keeps him busy.
>> That's a bit arrogant. You emailed only 4 days ago.
>> I'm open to do PR for rc3 with the fix, if it cannot wait to v6.4 pr.
> If this is about slow response with kernel bugzilla: [...]

Not at all, I don't care if developers use bugzilla or ignore it, as
long as the regression itself it dealt with.

Fun fact: I actually wanted to get rid of bugzilla for developers/
subsystems that didn't opt-in, but then another plan came up. See

Ciao, Thorsten

  parent reply	other threads:[~2023-03-12 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28  2:44 [PATCH v3] tpm: disable hwrng for fTPM on some AMD designs Mario Limonciello
2023-02-28  3:10 ` Jarkko Sakkinen
2023-03-08  9:42   ` Linux regression tracking (Thorsten Leemhuis)
2023-03-10 17:43     ` Thorsten Leemhuis
2023-03-12  1:35       ` Jarkko Sakkinen
2023-03-12  1:42         ` Jarkko Sakkinen
2023-03-12  1:49           ` Jason A. Donenfeld
2023-03-12  1:55             ` Jarkko Sakkinen
2023-03-12  1:57               ` Jarkko Sakkinen
2023-03-12 10:40           ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-03-12 10:35         ` Linux regression tracking (Thorsten Leemhuis)

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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.