From: Jarkko Sakkinen <jarkko@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
keyrings@vger.kernel.org, James Morris <jmorris@namei.org>,
David Howells <dhowells@redhat.com>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [GIT PULL] TPM DEVICE DRIVER updates for v5.18
Date: Thu, 10 Mar 2022 01:50:44 +0200 [thread overview]
Message-ID: <Yik9VIcfuhW5Kd73@kernel.org> (raw)
In-Reply-To: <YieldvygMyiqmZbT@iki.fi>
On Tue, Mar 08, 2022 at 08:50:30PM +0200, Jarkko Sakkinen wrote:
> On Tue, Mar 08, 2022 at 10:10:31AM -0800, Eric Biggers wrote:
> > On Tue, Mar 08, 2022 at 02:58:49PM +0200, Jarkko Sakkinen wrote:
> > > KEYS: asymmetric: enforce that sig algo matches key algo
> >
> > It looks like you applied v1 of this patch
> > (https://lore.kernel.org/r/20220201003414.55380-2-ebiggers@kernel.org) rather
> > than v2 (https://lore.kernel.org/r/20220208052448.409152-2-ebiggers@kernel.org).
> > I think that v2 is necessary because some callers of
> > public_key_verify_signature() leave pkey_algo as NULL.
> >
> > Sorry for not spotting that you applied v1 earlier.
> >
> > - Eric
>
> I can do another pull request.
Eric, does 'next' branch in
git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git
look good to you now?
BR, Jarkko
next prev parent reply other threads:[~2022-03-09 23:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 12:58 [GIT PULL] TPM DEVICE DRIVER updates for v5.18 Jarkko Sakkinen
2022-03-08 18:10 ` Eric Biggers
2022-03-08 18:50 ` Jarkko Sakkinen
2022-03-09 23:50 ` Jarkko Sakkinen [this message]
2022-03-10 4:20 ` Eric Biggers
2022-03-21 19:18 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-03-14 3:32 Jarkko Sakkinen
2022-03-14 3:38 ` Jarkko Sakkinen
2022-03-14 3:36 Jarkko Sakkinen
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=Yik9VIcfuhW5Kd73@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--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=peterhuewe@gmx.de \
--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).