From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Arnd Bergmann <arnd@kernel.org>, Peter Huewe <peterhuewe@gmx.de>,
Li Jun <lijun01@kylinos.cn>, Arnd Bergmann <arnd@arndb.de>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tpm: remove extraneous #ifdef
Date: Fri, 18 Sep 2026 07:44:30 +0200 [thread overview]
Message-ID: <aqzOnj9-35h3gAPD@monoceros> (raw)
In-Reply-To: <aqyOUgIa4lsUwO0I@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
Hello Jarkko,
On Fri, Sep 18, 2026 at 04:05:22AM +0300, Jarkko Sakkinen wrote:
> On Fri, Sep 18, 2026 at 04:01:57AM +0300, Jarkko Sakkinen wrote:
> > I pushed this to for-next-tpm, which mirrors to linux-next.
I don't spot it in
https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git for-next-tpm
, do I look at the wrong tree?
> > However, since this is -next only bug, I guess I should squash these to
> > the original commit?
> >
> > Just sanity checking before taking action :-)
>
> My suggestion would be to amend Co-authored-by to the original commit
> message as two bug fixes is significant amount of effort to make the
> change right.
I don't care much about my Tested-by: tag, so feel free to drop it.
Promoting that to a Tested-by: on the squashed commit is wrong for sure.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-18 5:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 20:12 Arnd Bergmann
2026-09-17 5:53 ` Uwe Kleine-König
2026-09-18 0:58 ` Jarkko Sakkinen
2026-09-18 1:01 ` Jarkko Sakkinen
2026-09-18 1:05 ` Jarkko Sakkinen
2026-09-18 5:44 ` Uwe Kleine-König [this message]
2026-09-18 5:49 ` Arnd Bergmann
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=aqzOnj9-35h3gAPD@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=lijun01@kylinos.cn \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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®