linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Laura Abbott <labbott@redhat.com>
Cc: "Winkler, Tomas" <tomas.winkler@intel.com>,
	Kees Cook <keescook@chromium.org>, Jason Gunthorpe <jgg@ziepe.ca>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Phil Baker <baker1tex@gmail.com>, Craig Robson <craig@zhatt.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Peter Huewe <peterhuewe@gmx.de>, Arnd Bergmann <arnd@arndb.de>,
	"linux-integrity@vger.kernel.org"
	<linux-integrity@vger.kernel.org>
Subject: Re: [PATCH v3] tpm: Actually fail on TPM errors during "get random"
Date: Wed, 29 May 2019 17:39:07 +0300	[thread overview]
Message-ID: <20190529143907.GA7984@linux.intel.com> (raw)
In-Reply-To: <bfcb58ef-98b3-a663-c249-3940ec9a39d3@redhat.com>

On Tue, May 28, 2019 at 03:02:49PM -0400, Laura Abbott wrote:
> > Great, I'll add it. Thank you. Just want to be explicit with these
> > things as I consider them as if I was asking a signature from someone
> > :-)
> > 
> > /Jarkko
> > 
> Was this intended to go in for 5.2? I still don't see it in the tree.

Was intended but I failed to notice that I should start to send PRs
to Linus instead of security tree and was waiting for security tree
to be rebased. I'll include to the next PR.

/Jarkko

      reply	other threads:[~2019-05-29 14:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 19:06 [PATCH v3] tpm: Actually fail on TPM errors during "get random" Kees Cook
2019-04-01 19:09 ` Jason Gunthorpe
2019-04-01 19:14   ` Kees Cook
2019-04-01 19:41 ` Winkler, Tomas
2019-04-01 23:46 ` Jarkko Sakkinen
2019-04-02 16:40   ` Jarkko Sakkinen
2019-04-02 19:13     ` Winkler, Tomas
2019-04-03 17:52       ` Jarkko Sakkinen
2019-05-28 19:02         ` Laura Abbott
2019-05-29 14:39           ` 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=20190529143907.GA7984@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=arnd@arndb.de \
    --cc=baker1tex@gmail.com \
    --cc=craig@zhatt.com \
    --cc=jgg@ziepe.ca \
    --cc=keescook@chromium.org \
    --cc=labbott@redhat.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=tomas.winkler@intel.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).