From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
David Howells <dhowells@redhat.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] tpmdd updates for v5.19-rc2
Date: Wed, 08 Jun 2022 14:06:48 +0300 [thread overview]
Message-ID: <830f58cbcae3275310fe8b132c8f7cb12842e0f4.camel@kernel.org> (raw)
In-Reply-To: <20220608092646.3074700-1-jarkko@kernel.org>
On Wed, 2022-06-08 at 12:26 +0300, Jarkko Sakkinen wrote:
> The following changes since commit 9886142c7a2226439c1e3f7d9b69f9c7094c3ef6:
>
> Merge tag 'input-for-v5.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input (2022-06-07 15:00:29 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/ tags/tpmdd-next-v5.19-rc2
>
> for you to fetch changes up to 967a4b757b51164a3dc3307234fcb48b7be2745b:
>
> KEYS: trusted: tpm2: Fix migratable logic (2022-06-08 12:13:26 +0300)
>
> ----------------------------------------------------------------
> A bug fix for migratable (whether or not a key is tied to the TPM chip
> soldered to the machine) handling for TPM2 trusted keys.
>
> ----------------------------------------------------------------
> david.safford@gmail.com (1):
> KEYS: trusted: tpm2: Fix migratable logic
>
> security/keys/trusted-keys/trusted_tpm2.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Ugh, from-address in malformed. I'll need to redo the PR.
BR, Jarkko
prev parent reply other threads:[~2022-06-08 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 9:26 [GIT PULL] tpmdd updates for v5.19-rc2 Jarkko Sakkinen
2022-06-08 11:06 ` Jarkko Sakkinen [this message]
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=830f58cbcae3275310fe8b132c8f7cb12842e0f4.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=serge@hallyn.com \
--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 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.