From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Seunghun Han <kkamagui@gmail.com>
Cc: ivan.lazeev@gmail.com, arnd@arndb.de, gregkh@linuxfoundation.org,
jgg@ziepe.ca, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org, peterhuewe@gmx.de
Subject: Re: [PATCH v2] Fix fTPM on AMD Zen+ CPUs
Date: Fri, 13 Sep 2019 15:02:18 +0100 [thread overview]
Message-ID: <20190913140218.GB29755@linux.intel.com> (raw)
In-Reply-To: <20190913140006.GA29755@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.
/Jarkko
next prev parent reply other threads:[~2019-09-13 14:02 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 [this message]
2019-09-16 5:29 ` Seunghun Han
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=20190913140218.GB29755@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=ivan.lazeev@gmail.com \
--cc=jgg@ziepe.ca \
--cc=kkamagui@gmail.com \
--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 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.