From: "Arnd Bergmann" <arnd@arndb.de>
To: "Qunqin Zhao" <zhaoqunqin@loongson.cn>,
"Lee Jones" <lee@kernel.org>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
"David S . Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org,
"derek.kiernan@amd.com" <derek.kiernan@amd.com>,
"dragan.cvetic@amd.com" <dragan.cvetic@amd.com>,
"Yinggang Gu" <guyinggang@loongson.cn>
Subject: Re: [PATCH v1 3/3] misc: ls6000se-sdf: Add driver for Loongson 6000SE SDF
Date: Tue, 14 Jan 2025 11:17:45 +0100 [thread overview]
Message-ID: <ee65851c-4149-4927-a2e7-356cdce2ba25@app.fastmail.com> (raw)
In-Reply-To: <20250114095527.23722-4-zhaoqunqin@loongson.cn>
On Tue, Jan 14, 2025, at 10:55, Qunqin Zhao wrote:
> Loongson Secure Device Function device supports the functions specified
> in "GB/T 36322-2018". This driver is only responsible for sending user
> data to SDF devices or returning SDF device data to users.
I haven't been able to find a public version of the standard, but
from the table of contents it sounds like this is a standard for
cryptographic functions that would otherwise be implemented by a
driver in drivers/crypto/ so it can use the normal abstractions
for both userspace and in-kernel users.
Is there some reason this doesn't work?
Arnd
next prev parent reply other threads:[~2025-01-14 10:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 9:55 [PATCH v1 0/3] Drivers for Loongson security engine Qunqin Zhao
2025-01-14 9:55 ` [PATCH v1 1/3] mfd: Add support for Loongson Security Module Qunqin Zhao
2025-01-14 9:55 ` [PATCH v1 2/3] crypto: loongson - add Loongson RNG driver support Qunqin Zhao
2025-01-14 9:55 ` [PATCH v1 3/3] misc: ls6000se-sdf: Add driver for Loongson 6000SE SDF Qunqin Zhao
2025-01-14 10:17 ` Arnd Bergmann [this message]
2025-01-14 10:43 ` Xi Ruoyao
2025-01-14 13:21 ` Greg Kroah-Hartman
2025-01-15 2:58 ` Qunqin Zhao
2025-01-15 7:58 ` Greg Kroah-Hartman
2025-01-15 10:39 ` Zheng, Yaofei
2025-01-15 11:13 ` Xi Ruoyao
2025-01-26 4:26 ` WANG Xuerui
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=ee65851c-4149-4927-a2e7-356cdce2ba25@app.fastmail.com \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=derek.kiernan@amd.com \
--cc=dragan.cvetic@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=guyinggang@loongson.cn \
--cc=herbert@gondor.apana.org.au \
--cc=lee@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--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