From: Jarkko Sakkinen <jarkko@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
stable@vger.kernel.org,
James Bottomley <James.Bottomley@hansenpartnership.com>,
reach622@mailcuk.com, Bell <1138267643@qq.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH v3] tpm: disable hwrng for fTPM on some AMD designs
Date: Sun, 12 Mar 2023 03:55:00 +0200 [thread overview]
Message-ID: <ZA0w9IjDqcm4YxhO@kernel.org> (raw)
In-Reply-To: <CAHmME9pudxP07Jx77yUecDLqm2xku3cPJFtk=bY6ACmfL1j5xw@mail.gmail.com>
On Sun, Mar 12, 2023 at 02:49:17AM +0100, Jason A. Donenfeld wrote:
> On 3/12/23, Jarkko Sakkinen <jarkko@kernel.org> 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: it is not *enforced*
> > part of the process. If it was, I would use it. Since it isn't, I don't
> > really want to add any extra weight to my workflow.
> >
> > It's not only extra time but also it is not documented how exactly and in
> > detail you would use it. For email we have all that documented. And when
> > you don't have guidelines, then it is too flakky to use properly.
>
> No interest in wading into a process argument. But if you're able to
> send this for rc3, please please do so. Users keep getting hit by
> this, some email me directly, and I keep replying saying the fix
> should be released any day now. So let's make that happen.
Sure, that shouldn't be a problem. I'll queue this for rc3.
BR, Jarkko
next prev parent reply other threads:[~2023-03-12 1:55 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 [this message]
2023-03-12 1:57 ` Jarkko Sakkinen
2023-03-12 10:40 ` Linux regression tracking (Thorsten Leemhuis)
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:
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=ZA0w9IjDqcm4YxhO@kernel.org \
--to=jarkko@kernel.org \
--cc=1138267643@qq.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=Jason@zx2c4.com \
--cc=herbert@gondor.apana.org.au \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mario.limonciello@amd.com \
--cc=peterhuewe@gmx.de \
--cc=reach622@mailcuk.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).