public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Qunqin Zhao <zhaoqunqin@loongson.cn>
Cc: lee@kernel.org, herbert@gondor.apana.org.au, davem@davemloft.net,
	peterhuewe@gmx.de, linux-kernel@vger.kernel.org,
	loongarch@lists.linux.dev, linux-crypto@vger.kernel.org,
	jgg@ziepe.ca, linux-integrity@vger.kernel.org,
	Yinggang Gu <guyinggang@loongson.cn>
Subject: Re: [PATCH v2 3/3] tpm: Add a driver for Loongson TPM device
Date: Fri, 14 Feb 2025 00:10:00 +0200	[thread overview]
Message-ID: <Z65tuC722nnuhWEO@kernel.org> (raw)
In-Reply-To: <c825cd7b-a255-d296-baa0-c1a746cb1bce@loongson.cn>

On Thu, Feb 13, 2025 at 11:56:25AM +0800, Qunqin Zhao wrote:
> 
> 在 2025/2/13 上午5:28, Jarkko Sakkinen 写道:
> > On Wed, Feb 12, 2025 at 11:31:13AM +0800, Qunqin Zhao wrote:
> > > TPM2.0 is implemented in Loongson security engine. This is the driver
> > TPM 2.0 or just TPM2 (either is fine with me). Quick reminder what
> > Loongson security engine (I could not know that and it would be nice
> > to have that in git log).
> 
> Looks like just TPM2 is better.

Either is fine :-)

> 
> Some explanations about Loongson security engine will be added to git log.
> 
> > 
> > > for it.
> > > 
> > > Co-developed-by: Yinggang Gu <guyinggang@loongson.cn>
> > > Signed-off-by: Yinggang Gu <guyinggang@loongson.cn>
> > > Signed-off-by: Qunqin Zhao <zhaoqunqin@loongson.cn>
> > > ---
> > >   MAINTAINERS                 |   1 +
> > >   drivers/char/tpm/Kconfig    |   9 ++++
> > >   drivers/char/tpm/Makefile   |   1 +
> > >   drivers/char/tpm/tpm_lsse.c | 104 ++++++++++++++++++++++++++++++++++++
> > >   4 files changed, 115 insertions(+)
> > >   create mode 100644 drivers/char/tpm/tpm_lsse.c
> > > 
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 6493d58436..6aad0f08ad 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -13484,6 +13484,7 @@ LOONGSON CRYPTO DRIVER
> > >   M:	Qunqin Zhao <zhaoqunqin@loongson.com>
> > >   L:	linux-crypto@vger.kernel.org
> > >   S:	Maintained
> > > +F:	drivers/char/tpm/tpm_lsse.c
> > >   F:	drivers/crypto/loongson/
> > >   LOONGSON-2 APB DMA DRIVER
> > Probably MAINTAINERS update should be a separate patch.
> 
> Some  MAINTAINERS updates are not  separated form the driver patch.  Like
> the submit of "drivers/mfd/max7714*".
> 
> So it seems whether the updates to MAINTAINERS  are separated or not is OK.

I'd prefer them separated from code changes. They are separate tasks
per se.

BR, Jarkko

  reply	other threads:[~2025-02-13 22:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12  3:31 [PATCH v2 0/3] Drivers for Loongson security engine Qunqin Zhao
2025-02-12  3:31 ` [PATCH v2 1/3] mfd: Add support for Loongson Security Module Qunqin Zhao
2025-02-12  3:31 ` [PATCH v2 2/3] crypto: loongson - add Loongson RNG driver support Qunqin Zhao
2025-02-12  3:31 ` [PATCH v2 3/3] tpm: Add a driver for Loongson TPM device Qunqin Zhao
2025-02-12 21:28   ` Jarkko Sakkinen
2025-02-13  3:56     ` Qunqin Zhao
2025-02-13 22:10       ` Jarkko Sakkinen [this message]
2025-02-14  1:12         ` Qunqin Zhao

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=Z65tuC722nnuhWEO@kernel.org \
    --to=jarkko@kernel.org \
    --cc=davem@davemloft.net \
    --cc=guyinggang@loongson.cn \
    --cc=herbert@gondor.apana.org.au \
    --cc=jgg@ziepe.ca \
    --cc=lee@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=peterhuewe@gmx.de \
    --cc=zhaoqunqin@loongson.cn \
    /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