From: Herbert Xu <herbert@gondor.apana.org.au>
To: AlanSong-oc <AlanSong-oc@zhaoxin.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
larryw3i <larryw3i@yeah.net>,
stable@vger.kernel.org, CobeChen@zhaoxin.com,
GeorgeXue@zhaoxin.com, HansHu@zhaoxin.com, LeoLiu-oc@zhaoxin.com,
TonyWWang-oc@zhaoxin.com, YunShen@zhaoxin.com
Subject: Re: [PATCH] crypto: padlock-sha - Disable broken driver
Date: Wed, 17 Dec 2025 12:56:40 +0800 [thread overview]
Message-ID: <aUI4CGp6kK7mxgEr@gondor.apana.org.au> (raw)
In-Reply-To: <cd6a8143-f93a-4843-b8f6-dbff645c7555@zhaoxin.com>
On Wed, Dec 17, 2025 at 12:30:57PM +0800, AlanSong-oc wrote:
>
> Given the lack of a verification platform for the current padlock-sha
> driver, and the fact that these CPUs are rarely used today, extending
> the existing padlock-sha driver to support the ZHAOXIN platform is very
> difficult. To address the issues encountered when using the padlock-sha
> driver on the ZHAOXIN platform, would it be acceptable to submit a
> completely new driver that aligns with the previous advice?
Perhaps it would be easier if you just added Zhaoxin support to
lib/crypto instead?
Cheers,
--
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
next prev parent reply other threads:[~2025-12-17 4:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a1ed50c2-7338-4c97-8c36-84d2fa83d018@yeah.net>
2025-11-16 15:50 ` linux-image-amd64: self-tests for sha256 using sha256-padlock-nano failed larryw3i
2025-11-16 18:39 ` [PATCH] crypto: padlock-sha - Disable broken driver Eric Biggers
2025-11-17 9:03 ` AlanSong-oc
2025-11-17 10:08 ` larryw3i
2025-11-18 8:22 ` AlanSong-oc
2025-11-19 3:41 ` larryw3i
2025-11-18 3:34 ` Herbert Xu
2025-11-18 4:02 ` Eric Biggers
2025-12-17 4:30 ` AlanSong-oc
2025-12-17 4:56 ` Herbert Xu [this message]
2025-12-17 9:04 ` AlanSong-oc
2026-01-06 14:47 ` larryw3i
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=aUI4CGp6kK7mxgEr@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=AlanSong-oc@zhaoxin.com \
--cc=CobeChen@zhaoxin.com \
--cc=GeorgeXue@zhaoxin.com \
--cc=HansHu@zhaoxin.com \
--cc=LeoLiu-oc@zhaoxin.com \
--cc=TonyWWang-oc@zhaoxin.com \
--cc=YunShen@zhaoxin.com \
--cc=ebiggers@kernel.org \
--cc=larryw3i@yeah.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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.