From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-integrity@vger.kernel.org
Subject: Re: [PATCH] tpm: only export stand alone version of flush context command
Date: Tue, 29 Sep 2020 01:12:02 +0300 [thread overview]
Message-ID: <20200928221202.GH2705@linux.intel.com> (raw)
In-Reply-To: <6720ff958180a9e040c655dcfc281b3260fe88f2.camel@HansenPartnership.com>
On Mon, Sep 28, 2020 at 11:26:41AM -0700, James Bottomley wrote:
> > Yes.
> >
> > BTW, while doing this I think I noticed what was wrong in my test
> > kernel when I tested your series that introduces ASN.1 keys. I'll
> > test both before sending update to my fix. Hopefully I can give today
> > tested-by tags to that series.
>
> Great ... the trusted key code doesn't use tpm_send, but the policy
> additions do so the latter will need updating (again).
Yes, I know. I can still test both by separately applying them on top
of the current master. If you can after that do the update (and after
the fixes have been applied), I can still get everything to the same
PR.
Sorry for latency because of some SGX discussions (this time retpoline
and CET collision), I'll try to get the testing done ASAP.
/Jarkko
prev parent reply other threads:[~2020-09-28 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 23:17 [PATCH] tpm: only export stand alone version of flush context command James Bottomley
2020-09-28 0:11 ` Jarkko Sakkinen
2020-09-28 1:03 ` James Bottomley
2020-09-28 11:20 ` Jarkko Sakkinen
2020-09-28 11:34 ` Jarkko Sakkinen
2020-09-28 12:28 ` Jarkko Sakkinen
2020-09-28 14:50 ` James Bottomley
2020-09-28 16:31 ` Jarkko Sakkinen
2020-09-28 17:07 ` Jarkko Sakkinen
2020-09-28 17:40 ` James Bottomley
2020-09-28 18:13 ` Jarkko Sakkinen
2020-09-28 18:26 ` James Bottomley
2020-09-28 22:12 ` 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=20200928221202.GH2705@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-integrity@vger.kernel.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).