From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-stable@vger.kernel.org, Peter Huewe <peterhuewe@gmx.de>,
Jason Gunthorpe <jgg@ziepe.ca>, Arnd Bergmann <arnd@arndb.de>,
"open list:TPM DEVICE DRIVER" <linux-integrity@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/3] tpm: migrate pubek_show to struct tpm_buf
Date: Thu, 10 Oct 2019 10:27:25 +0200 [thread overview]
Message-ID: <20191010082725.GA326087@kroah.com> (raw)
In-Reply-To: <20191009212831.29081-2-jarkko.sakkinen@linux.intel.com>
On Thu, Oct 10, 2019 at 12:28:29AM +0300, Jarkko Sakkinen wrote:
> commit da379f3c1db0c9a1fd27b11d24c9894b5edc7c75 upstream
>
> Migrated pubek_show to struct tpm_buf and cleaned up its implementation.
> Previously the output parameter structure was declared but left
> completely unused. Now it is used to refer different fields of the
> output. We can move it to tpm-sysfs.c as it does not have any use
> outside of that file.
>
> Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> ---
> drivers/char/tpm/tpm-sysfs.c | 87 ++++++++++++++++++++----------------
> drivers/char/tpm/tpm.h | 13 ------
> 2 files changed, 48 insertions(+), 52 deletions(-)
This is already in the 4.14.148 kernel release.
Why do we need it again?
Also, the mailing list is stable@vger, not linux-stable@vger.
thanks,
greg k-h
next prev parent reply other threads:[~2019-10-10 8:27 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 [this message]
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
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=20191010082725.GA326087@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stable@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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.