From: Sumit Garg <sumit.garg@linaro.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: jejb@linux.ibm.com, Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org, dhowells@redhat.com
Subject: Re: KEYS-TRUSTED git
Date: Wed, 11 Sep 2019 16:58:27 +0530 [thread overview]
Message-ID: <CAFA6WYNF0=q-rsOgv0Nuepbz_7Z50US6um7e6eWjm=E-eR+NpQ@mail.gmail.com> (raw)
In-Reply-To: <CAFA6WYOdgxEjCYMsgqCUjq7mydH3apxmqxjkyLbqiKfc_1R5Tg@mail.gmail.com>
On Wed, 11 Sep 2019 at 15:28, Sumit Garg <sumit.garg@linaro.org> wrote:
>
> On Wed, 11 Sep 2019 at 15:06, Jarkko Sakkinen
> <jarkko.sakkinen@linux.intel.com> wrote:
> >
> > On Wed, Sep 11, 2019 at 10:29:26AM +0100, Jarkko Sakkinen wrote:
> > > On Wed, Sep 11, 2019 at 10:27:08AM +0100, Jarkko Sakkinen wrote:
> > > > On Tue, Sep 10, 2019 at 12:43:36PM +0100, Jarkko Sakkinen wrote:
> > > > > On Mon, Sep 09, 2019 at 11:57:45AM +0530, Sumit Garg wrote:
> > > > > > @Jarkko: No worries, I understand the situation.
> > > > >
> > > > > I made the call to add them anyway to my TPM tree.
> > > >
> > > > Also,
> > > >
> > > > Tested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > > >
> > > > I think I give a shot of doing one more PR to 5.4 because that would
> > > > help both your and James' work because this is the kind of intersection
> > > > point betwen them.
> > >
> > > Polished short summaries a bit:
> > >
> > > 1. Start with capital letter.
> > > 2. s/tpm2/TPM2/g
> >
> > Now also in my next branch. I wait for 24h or so and if no alarms are
> > rised I'll send a PR. The code changes for the most part mechanically
> > move stuff, which makes me confident that I can still do a PR with
> > these changes.
>
> Did you notice an issue reported by kbuild test robot? It looks like
> asymmetric keys based on TPM also relied on old tpm_buf method. So we
> need to transition them also to use new tpm_buf method. I can work on
> corresponding changes required but need your help to test it.
>
Patch: https://lkml.org/lkml/2019/9/11/312 to transition TPM
asymmetric keys code.
-Sumit
>
> >
> > /Jarkko
next prev parent reply other threads:[~2019-09-11 11:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 0:10 KEYS-TRUSTED git Jarkko Sakkinen
2019-09-08 14:20 ` Mimi Zohar
2019-09-09 6:27 ` Sumit Garg
2019-09-09 10:40 ` Mimi Zohar
2019-09-09 16:36 ` Jarkko Sakkinen
2019-09-10 5:13 ` Sumit Garg
2019-09-13 13:34 ` Jarkko Sakkinen
2019-09-10 11:43 ` Jarkko Sakkinen
2019-09-10 12:32 ` Sumit Garg
2019-09-11 9:27 ` Jarkko Sakkinen
2019-09-11 9:29 ` Jarkko Sakkinen
2019-09-11 9:36 ` Jarkko Sakkinen
2019-09-11 9:58 ` Sumit Garg
2019-09-11 11:28 ` Sumit Garg [this message]
2019-09-09 16:33 ` Jarkko Sakkinen
2019-09-09 16:52 ` Jarkko Sakkinen
2019-09-09 17:24 ` Mimi Zohar
2019-09-13 13:32 ` Jarkko Sakkinen
2019-09-15 20:53 ` Mimi Zohar
2019-09-10 14:21 ` 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='CAFA6WYNF0=q-rsOgv0Nuepbz_7Z50US6um7e6eWjm=E-eR+NpQ@mail.gmail.com' \
--to=sumit.garg@linaro.org \
--cc=dhowells@redhat.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jejb@linux.ibm.com \
--cc=linux-integrity@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).