From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Doug Anderson <dianders@chromium.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, "# 4.0+" <stable@vger.kernel.org>,
Guenter Roeck <groeck@chromium.org>,
Vadim Sukhomlinov <sukhomlinov@google.com>,
Arnd Bergmann <arnd@arndb.de>, Peter Huewe <peterhuewe@gmx.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations
Date: Fri, 12 Jul 2019 18:21:56 +0300 [thread overview]
Message-ID: <b5a73063fe855e027623c211e6ea5c7d20a27a04.camel@linux.intel.com> (raw)
In-Reply-To: <20190712115025.GA8221@kroah.com>
On Fri, 2019-07-12 at 13:50 +0200, Greg KH wrote:
> But the sysfs comment means I should not apply this backport then?
>
> Totally confused by this long thread, sorry.
>
> What am I supposed to do for the stable trees here?
I'll work out a proper patch set for stable kernels with necessary
patches and cover letter with a brief summary in the week starting
29th of this month when I come back from vacation.
/Jarkko
next prev parent reply other threads:[~2019-07-12 15:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 16:29 [PATCH] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations Douglas Anderson
2019-07-11 16:39 ` Jason Gunthorpe
2019-07-11 16:41 ` Doug Anderson
2019-07-11 17:04 ` Greg KH
2019-07-11 17:17 ` Jason Gunthorpe
2019-07-11 17:26 ` Greg KH
2019-07-11 17:28 ` Doug Anderson
2019-07-12 11:50 ` Greg KH
2019-07-12 15:00 ` Doug Anderson
2019-07-12 15:27 ` Greg KH
2019-08-05 21:05 ` Jarkko Sakkinen
2019-07-12 15:47 ` Jarkko Sakkinen
2019-07-12 15:21 ` Jarkko Sakkinen [this message]
2019-07-11 18:35 ` Jarkko Sakkinen
2019-07-11 19:43 ` Jarkko Sakkinen
2019-07-11 19:46 ` Jason Gunthorpe
2019-07-12 3:31 ` Jarkko Sakkinen
2019-07-12 3:35 ` Jarkko Sakkinen
2019-07-12 11:58 ` Jason Gunthorpe
2019-07-11 19:55 ` Doug Anderson
2019-07-11 18:34 ` 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=b5a73063fe855e027623c211e6ea5c7d20a27a04.camel@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=arnd@arndb.de \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=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 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).