> And also
>
> Tested-by: Sahil Rihan
Sure!
> And also
>
> Tested-by: Sahil Rihan
Sure!
On Tue, Mar 27, 2018 at 12:07:14AM +, Sahil Rihan wrote:
> > On 3/22/18, 7:20 AM, "Jarkko Sakkinen"
> > wrote:
> >
> > On Tue, 2018-03-20 at 22:29 +, Sahil Rihan wrote:
> > > > On 3/19/18, 2:25 PM, "Jarkko Sakkinen"
> >
On Tue, Mar 27, 2018 at 12:07:14AM +, Sahil Rihan wrote:
> > On 3/22/18, 7:20 AM, "Jarkko Sakkinen"
> > wrote:
> >
> > On Tue, 2018-03-20 at 22:29 +, Sahil Rihan wrote:
> > > > On 3/19/18, 2:25 PM, "Jarkko Sakkinen"
> >
> > > > wrote:
> > > >
> > > >Sahil, would you
> On 3/22/18, 7:20 AM, "Jarkko Sakkinen"
> wrote:
>
> On Tue, 2018-03-20 at 22:29 +, Sahil Rihan wrote:
> > > On 3/19/18, 2:25 PM, "Jarkko Sakkinen"
> > > wrote:
> > >
> > >Sahil, would you care to try if
> On 3/22/18, 7:20 AM, "Jarkko Sakkinen"
> wrote:
>
> On Tue, 2018-03-20 at 22:29 +, Sahil Rihan wrote:
> > > On 3/19/18, 2:25 PM, "Jarkko Sakkinen"
> > > wrote:
> > >
> > >Sahil, would you care to try if this fixes the issue that you are
> > >having or not?
> >
On Tue, 2018-03-20 at 22:29 +, Sahil Rihan wrote:
> > On 3/19/18, 2:25 PM, "Jarkko Sakkinen"
> > wrote:
> >
> >Sahil, would you care to try if this fixes the issue that you are
> >having or not?
>
> Yes, we can test this out. Might take a day or
On Tue, 2018-03-20 at 22:29 +, Sahil Rihan wrote:
> > On 3/19/18, 2:25 PM, "Jarkko Sakkinen"
> > wrote:
> >
> >Sahil, would you care to try if this fixes the issue that you are
> >having or not?
>
> Yes, we can test this out. Might take a day or two.
Awesome, thank you. I'll
> On 3/19/18, 2:25 PM, "Jarkko Sakkinen"
> wrote:
>
>Sahil, would you care to try if this fixes the issue that you are
>having or not?
Yes, we can test this out. Might take a day or two.
Sahil
> On 3/19/18, 2:25 PM, "Jarkko Sakkinen"
> wrote:
>
>Sahil, would you care to try if this fixes the issue that you are
>having or not?
Yes, we can test this out. Might take a day or two.
Sahil
On Sun, Mar 18, 2018 at 08:13:23PM -0600, Jason Gunthorpe wrote:
> On Fri, Mar 16, 2018 at 02:55:25PM +0200, Jarkko Sakkinen wrote:
> > On Mon, Mar 12, 2018 at 09:02:32AM -0600, Jason Gunthorpe wrote:
> > > On Sat, Mar 10, 2018 at 06:16:37PM +0200, Jarkko Sakkinen wrote:
> > > > TCPA log are can
On Sun, Mar 18, 2018 at 08:13:23PM -0600, Jason Gunthorpe wrote:
> On Fri, Mar 16, 2018 at 02:55:25PM +0200, Jarkko Sakkinen wrote:
> > On Mon, Mar 12, 2018 at 09:02:32AM -0600, Jason Gunthorpe wrote:
> > > On Sat, Mar 10, 2018 at 06:16:37PM +0200, Jarkko Sakkinen wrote:
> > > > TCPA log are can
On Fri, Mar 16, 2018 at 02:55:25PM +0200, Jarkko Sakkinen wrote:
> On Mon, Mar 12, 2018 at 09:02:32AM -0600, Jason Gunthorpe wrote:
> > On Sat, Mar 10, 2018 at 06:16:37PM +0200, Jarkko Sakkinen wrote:
> > > TCPA log are can be empty when the TPM is disabled. This commit changes
> > > the
> > >
On Fri, Mar 16, 2018 at 02:55:25PM +0200, Jarkko Sakkinen wrote:
> On Mon, Mar 12, 2018 at 09:02:32AM -0600, Jason Gunthorpe wrote:
> > On Sat, Mar 10, 2018 at 06:16:37PM +0200, Jarkko Sakkinen wrote:
> > > TCPA log are can be empty when the TPM is disabled. This commit changes
> > > the
> > >
On Mon, Mar 12, 2018 at 09:02:32AM -0600, Jason Gunthorpe wrote:
> On Sat, Mar 10, 2018 at 06:16:37PM +0200, Jarkko Sakkinen wrote:
> > TCPA log are can be empty when the TPM is disabled. This commit changes the
> > behavior of tpm_read_log_acpi() to return successfully in this case.
>
> The
On Mon, Mar 12, 2018 at 09:02:32AM -0600, Jason Gunthorpe wrote:
> On Sat, Mar 10, 2018 at 06:16:37PM +0200, Jarkko Sakkinen wrote:
> > TCPA log are can be empty when the TPM is disabled. This commit changes the
> > behavior of tpm_read_log_acpi() to return successfully in this case.
>
> The
On Sat, Mar 10, 2018 at 06:16:37PM +0200, Jarkko Sakkinen wrote:
> TCPA log are can be empty when the TPM is disabled. This commit changes the
> behavior of tpm_read_log_acpi() to return successfully in this case.
The commit should explain why we'd want this..
eg Why does it matter to create the
On Sat, Mar 10, 2018 at 06:16:37PM +0200, Jarkko Sakkinen wrote:
> TCPA log are can be empty when the TPM is disabled. This commit changes the
> behavior of tpm_read_log_acpi() to return successfully in this case.
The commit should explain why we'd want this..
eg Why does it matter to create the
On Sat, Mar 10, 2018 at 06:16:37PM +0200, Jarkko Sakkinen wrote:
> TCPA log are can be empty when the TPM is disabled. This commit changes the
> behavior of tpm_read_log_acpi() to return successfully in this case.
>
> Cc: sta...@vger.kernel.org
> Fixes: 55a82ab3181b ("[PATCH] tpm: add bios
On Sat, Mar 10, 2018 at 06:16:37PM +0200, Jarkko Sakkinen wrote:
> TCPA log are can be empty when the TPM is disabled. This commit changes the
> behavior of tpm_read_log_acpi() to return successfully in this case.
>
> Cc: sta...@vger.kernel.org
> Fixes: 55a82ab3181b ("[PATCH] tpm: add bios
TCPA log are can be empty when the TPM is disabled. This commit changes the
behavior of tpm_read_log_acpi() to return successfully in this case.
Cc: sta...@vger.kernel.org
Fixes: 55a82ab3181b ("[PATCH] tpm: add bios measurement log")
Signed-off-by: Jarkko Sakkinen
TCPA log are can be empty when the TPM is disabled. This commit changes the
behavior of tpm_read_log_acpi() to return successfully in this case.
Cc: sta...@vger.kernel.org
Fixes: 55a82ab3181b ("[PATCH] tpm: add bios measurement log")
Signed-off-by: Jarkko Sakkinen
---
22 matches
Mail list logo