[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f82e5d10-4300-4f7a-befe-fed524b52d92@zhaoxin.com>
Date: Wed, 17 Dec 2025 17:04:25 +0800
From: AlanSong-oc <AlanSong-oc@...oxin.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
CC: Eric Biggers <ebiggers@...nel.org>, <linux-crypto@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, larryw3i <larryw3i@...h.net>,
<stable@...r.kernel.org>, <CobeChen@...oxin.com>, <GeorgeXue@...oxin.com>,
<HansHu@...oxin.com>, <LeoLiu-oc@...oxin.com>, <TonyWWang-oc@...oxin.com>,
<YunShen@...oxin.com>
Subject: Re: [PATCH] crypto: padlock-sha - Disable broken driver
On 12/17/2025 12:56 PM, Herbert Xu wrote:
> 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?
Sincere thanks for your helpful suggestion. I will add ZHAOXIN platform
support to lib/crypto.
Best Regards
AlanSong-oc
Powered by blists - more mailing lists