All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Matthew Garrett <mjg59@google.com>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH V2] tpm: Don't make log failures fatal
Date: Fri, 21 Feb 2020 00:26:38 +0200	[thread overview]
Message-ID: <20200220222638.GA28411@linux.intel.com> (raw)
In-Reply-To: <CACdnJuvJyE7u+HSonm7-AcK9EabZobn46vEFVdrTSRcwNvz0_A@mail.gmail.com>

On Thu, Feb 20, 2020 at 12:29:24PM -0800, Matthew Garrett wrote:
> On Fri, Jan 3, 2020 at 3:26 PM Jarkko Sakkinen
> <jarkko.sakkinen@linux.intel.com> wrote:
> >
> > On Thu, 2020-01-02 at 13:55 -0800, Matthew Garrett wrote:
> > > If a TPM is in disabled state, it's reasonable for it to have an empty
> > > log. Bailing out of probe in this case means that the PPI interface
> > > isn't available, so there's no way to then enable the TPM from the OS.
> > > In general it seems reasonable to ignore log errors - they shouldn't
> > > interfere with any other TPM functionality.
> > >
> > > Signed-off-by: Matthew Garrett <mjg59@google.com>
> > > Cc: stable@vger.kernel.org
> >
> > Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> 
> Hi Jarkko,
> 
> Is this queued anywhere? Thanks!

Thanks for reminding. Now is:

git://git.infradead.org/users/jjs/linux-tpmdd.git

/Jarkko

  reply	other threads:[~2020-02-20 22:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 21:55 [PATCH V2] tpm: Don't make log failures fatal Matthew Garrett
2020-01-03 19:09 ` Jerry Snitselaar
2020-01-03 22:53 ` Jarkko Sakkinen
2020-02-20 20:29   ` Matthew Garrett
2020-02-20 22:26     ` Jarkko Sakkinen [this message]
     [not found] ` <20200104053108.B393D2071A@mail.kernel.org>
2020-02-20 20:22   ` Matthew Garrett
2020-02-25 10:42     ` Jarkko Sakkinen

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=20200220222638.GA28411@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=mjg59@google.com \
    --cc=stable@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 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.