From: Seunghun Han <kkamagui@gmail.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Vanya Lazeev <ivan.lazeev@gmail.com>,
arnd@arndb.de, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
"open list:TPM DEVICE DRIVER" <linux-integrity@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Huewe <peterhuewe@gmx.de>
Subject: Re: [PATCH v2] Fix fTPM on AMD Zen+ CPUs
Date: Mon, 16 Sep 2019 14:29:01 +0900 [thread overview]
Message-ID: <CAHjaAcSBCDnn7CwXfxYcfmRnAF2jdud1Sjwng_jtd8ASVS28Sg@mail.gmail.com> (raw)
In-Reply-To: <20190913140218.GB29755@linux.intel.com>
>
> On Fri, Sep 13, 2019 at 03:00:06PM +0100, Jarkko Sakkinen wrote:
> > On Wed, Sep 11, 2019 at 02:17:48PM +0900, Seunghun Han wrote:
> > > Vanya,
> > > I also made a patch series to solve AMD's fTPM. My patch link is here,
> > > https://lkml.org/lkml/2019/9/9/132 .
> > >
> > > The maintainer, Jarkko, wanted me to remark on your patch, so I would
> > > like to cooperate with you.
> > >
> > > Your patch is good for me. If you are fine, I would like to take your
> > > patch and merge it with my patch series. I also would like to change
> > > some points Jason mentioned before.
> >
> > I rather handle the review processes separately because I can merge
> > Vanyas's patch first. Bundling them into patch set would only slow
> > down things.
>
> I did not ask to do anything. I just review code changes.
I got it. I should concentrate on my ACPI NVS problem.
Thank you.
Seunghun
next prev parent reply other threads:[~2019-09-16 5:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 5:17 [PATCH v2] Fix fTPM on AMD Zen+ CPUs Seunghun Han
2019-09-13 14:00 ` Jarkko Sakkinen
2019-09-13 14:02 ` Jarkko Sakkinen
2019-09-16 5:29 ` Seunghun Han [this message]
2019-09-16 9:07 ` Jarkko Sakkinen
2019-09-16 9:43 ` Seunghun Han
-- strict thread matches above, loose matches on Subject: below --
2019-08-11 18:52 ivan.lazeev
2019-08-12 13:10 ` Jason Gunthorpe
2019-08-12 22:42 ` Vanya Lazeev
2019-08-15 20:47 ` 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=CAHjaAcSBCDnn7CwXfxYcfmRnAF2jdud1Sjwng_jtd8ASVS28Sg@mail.gmail.com \
--to=kkamagui@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=ivan.lazeev@gmail.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@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).