mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Qunqin Zhao <zhaoqunqin@loongson.cn>
Cc: Huacai Chen <chenhuacai@kernel.org>,
	davem@davemloft.net, peterhuewe@gmx.de, jarkko@kernel.org,
	linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
	linux-crypto@vger.kernel.org, jgg@ziepe.ca,
	linux-integrity@vger.kernel.org, pmenzel@molgen.mpg.de,
	Lee Jones <lee@kernel.org>
Subject: Re: [PATCH v8 0/5] Add Loongson Security Engine chip driver
Date: Wed, 30 Apr 2025 16:18:34 +0800	[thread overview]
Message-ID: <aBHc2tT2-Duj3_-A@gondor.apana.org.au> (raw)
In-Reply-To: <75bb29fa-6d77-6f95-eec4-ee183190da17@loongson.cn>

On Wed, Apr 30, 2025 at 04:14:40PM +0800, Qunqin Zhao wrote:
>
> Sorry to bother you, may i ask is it fine to move  the Security Engine base
> driver[Patch v8 1/5] to drivers/crypto ?
> 
> The base driver uses MFD  interface  to register child device(tpm, rng) , as
> done in
> 
> "drivers/iio/common/ssp_sensors/ssp_dev.c" and
> "drivers/firmware/xilinx/zynqmp.c".
> 
> Thank you, and I look forward to hearing from you.

I don't mind at this point in time.  But if this driver were to
develop features way outside of the Crypto API in future then I
may change my mind.

Thanks,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2025-04-30  8:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18  9:35 Qunqin Zhao
2025-04-20  7:17 ` Huacai Chen
2025-04-30  8:14   ` Qunqin Zhao
2025-04-30  8:18     ` Herbert Xu [this message]
2025-04-30  8:45       ` Qunqin Zhao
2025-04-30  8:53         ` Huacai Chen
2025-04-30  8:58           ` Lee Jones
2025-04-30  9:10             ` Qunqin Zhao
  -- strict thread matches above, loose matches on Subject: below --
2025-04-18  9:34 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=aBHc2tT2-Duj3_-A@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=chenhuacai@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jarkko@kernel.org \
    --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=pmenzel@molgen.mpg.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
all inboxes | Powered by JetHome®