mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Justin Forbes" <jforbes@fedoraproject.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Peter Huewe" <peterhuewe@gmx.de>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"David Howells" <dhowells@redhat.com>,
	"Mimi Zohar" <zohar@linux.ibm.com>,
	<linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<keyrings@vger.kernel.org>
Subject: Re: [GIT PULL] tpmdd changes for v6.6-rc2
Date: Fri, 15 Sep 2023 00:18:31 +0300	[thread overview]
Message-ID: <CVIYC7CUJOWH.FSY1TNPSHVX7@suppilovahvero> (raw)
In-Reply-To: <CAFbkSA1vh+PS7HxhdZ2jLer4ZPQJWTsSU5NEAwJW2Rp8CZwzZQ@mail.gmail.com>

On Fri Sep 15, 2023 at 12:05 AM EEST, Justin Forbes wrote:
> On Thu, Sep 14, 2023 at 4:02 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > On Wed, 13 Sept 2023 at 12:32, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> > >
> > > Ok, I'll make something more reasonable.
> >
> > Well, I took the pull already, just saying "tpm fix".
> >
> > I assume the only thing the typo actually causes is printk's with a
> > typo in it. Maybe some sysfs name will be wrong?
> >
> > That's the kind of information I would have _liked_ to see in the
> > merge message, but I didn't then delve into just where the class names
> > might actually be used.
>
> Sorry, I should have been more clear. The typo causes misnamed sysfs
> files, which breaks some userspace tools.

Ya, I got a bit confused because I assumed that the original change was
coming from my tree at first, and was wondering how could possibly my
QA process did not catch it. Should have checked in detail and wrote a
better description to the pull request. All in all, great that the issue
was catched before the release :-)

In future I suggest to run always the tpm2 test from kselftest's for any
TPM patch. It would have catched the bug early on.

BR, Jarkko

  reply	other threads:[~2023-09-14 21:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 20:11 Jarkko Sakkinen
2023-09-13 18:51 ` Linus Torvalds
2023-09-13 19:32   ` Jarkko Sakkinen
2023-09-13 19:45     ` Linus Torvalds
2023-09-13 19:54       ` Jarkko Sakkinen
2023-09-14 21:05       ` Justin Forbes
2023-09-14 21:18         ` Jarkko Sakkinen [this message]
2023-09-13 19:44 ` pr-tracker-bot

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=CVIYC7CUJOWH.FSY1TNPSHVX7@suppilovahvero \
    --to=jarkko@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=jforbes@fedoraproject.org \
    --cc=jgg@ziepe.ca \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=torvalds@linux-foundation.org \
    --cc=zohar@linux.ibm.com \
    /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

all inboxes | Powered by JetHome®