From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-stable@vger.kernel.org, linux-integrity@vger.kernel.org,
Vadim Sukhomlinov <sukhomlinov@google.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations
Date: Mon, 14 Oct 2019 13:39:26 +0300 [thread overview]
Message-ID: <20191014103926.GB12301@linux.intel.com> (raw)
In-Reply-To: <20191010082822.GD326087@kroah.com>
On Thu, Oct 10, 2019 at 10:28:22AM +0200, Greg KH wrote:
> On Thu, Oct 10, 2019 at 12:28:28AM +0300, Jarkko Sakkinen wrote:
> > commit db4d8cb9c9f2af71c4d087817160d866ed572cc9 upstream
> >
> > This backport is for v4.14 and v4.19 The backport requires non-racy
> > behaviour from TPM 1.x sysfs code. Thus, the dependecies for that
> > are included.
> >
> > NOTE: 1/3 is only needed for v4.14.
>
> How can a 0/X have a git commit id?
>
> :)
>
> greg k-h
It cannot. I just mentioned it here because the whole purpose
of two other dependecies is to support the backport of that
upstream commit.
/Jarkko.
prev parent reply other threads:[~2019-10-14 10:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 21:28 [PATCH v4 0/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations Jarkko Sakkinen
2019-10-09 21:28 ` [PATCH v4 1/3] tpm: migrate pubek_show to struct tpm_buf Jarkko Sakkinen
2019-10-10 8:27 ` Greg Kroah-Hartman
2019-10-09 21:28 ` [PATCH v4 2/3] tpm: use tpm_try_get_ops() in tpm-sysfs.c Jarkko Sakkinen
2019-10-10 8:27 ` Greg Kroah-Hartman
2019-10-09 21:28 ` [PATCH v4 3/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations Jarkko Sakkinen
2019-10-10 8:28 ` Greg Kroah-Hartman
2019-10-14 10:38 ` Jarkko Sakkinen
2019-10-10 8:28 ` [PATCH v4 0/3] " Greg KH
2019-10-14 10: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=20191014103926.GB12301@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stable@vger.kernel.org \
--cc=sukhomlinov@google.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 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.