Message ID | 20191009212831.29081-1-jarkko.sakkinen@linux.intel.com (mailing list archive) |
---|---|
Headers | show |
Series | tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations | expand |
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
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.