From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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 1/3] tpm: migrate pubek_show to struct tpm_buf
Date: Thu, 3 Oct 2019 20:56:03 +0300 [thread overview]
Message-ID: <20191003175603.GA19679@linux.intel.com> (raw)
In-Reply-To: <20191003113112.GB2447460@kroah.com>
On Thu, Oct 03, 2019 at 01:31:12PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Oct 03, 2019 at 02:24:22PM +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(-)
>
> Again, what kernel tree(s) do you want this, and the other 2 patches
> applied to? And why?
>
> thanks,
>
> greg k-h
D'oh, this is the cover letter:
https://patchwork.kernel.org/cover/11172533/
Looks like somehow forgot to include cc's, which were in the first
version:
Cc: linux-integrity@vger.kernel.org
Cc: Greg KH <gregkh@linuxfoundation.org>
Cc: Vadim Sukhomlinov <sukhomlinov@google.com>
Link: https://lore.kernel.org/stable/20190712152734.GA13940@kroah.com/
/Jarkko
next prev parent reply other threads:[~2019-10-03 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 11:24 [PATCH 0/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations Jarkko Sakkinen
2019-10-03 11:24 ` [PATCH 1/3] tpm: migrate pubek_show to struct tpm_buf Jarkko Sakkinen
2019-10-03 11:31 ` Greg Kroah-Hartman
2019-10-03 17:56 ` Jarkko Sakkinen [this message]
2019-10-03 11:24 ` [PATCH 2/3] tpm: use tpm_try_get_ops() in tpm-sysfs.c Jarkko Sakkinen
2019-10-03 11:24 ` [PATCH 3/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
2019-10-02 13:14 [PATCH 0/3] " Jarkko Sakkinen
2019-10-02 13:14 ` [PATCH 1/3] tpm: migrate pubek_show to struct tpm_buf Jarkko Sakkinen
2019-09-25 10:15 [PATCH 0/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations Jarkko Sakkinen
2019-09-25 10:15 ` [PATCH 1/3] tpm: migrate pubek_show to struct tpm_buf Jarkko Sakkinen
2019-09-24 14:01 [PATCH 0/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations Jarkko Sakkinen
2019-09-24 14:02 ` [PATCH 1/3] tpm: migrate pubek_show to struct tpm_buf 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=20191003175603.GA19679@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--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 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).