The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jia Jie Ho <jiajie.ho@starfivetech.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S . Miller" <davem@davemloft.net>,
	<linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH 2/2] crypto: starfive - Add RSA algo support
Date: Thu, 25 May 2023 09:56:03 +0800	[thread overview]
Message-ID: <29d515ec-83aa-c13e-b491-bc2ab7454012@starfivetech.com> (raw)
In-Reply-To: <ZG3biep8vAWQ5ZgA@gondor.apana.org.au>

On 24/5/2023 5:40 pm, Herbert Xu wrote:
> On Tue, May 16, 2023 at 03:57:52PM +0800, Jia Jie Ho wrote:
>>
>> +static struct akcipher_alg starfive_rsa = {
>> +	.encrypt = starfive_rsa_enc,
>> +	.decrypt = starfive_rsa_dec,
>> +	.sign = starfive_rsa_dec,
>> +	.verify = starfive_rsa_enc,
>> +	.set_pub_key = starfive_rsa_set_pub_key,
>> +	.set_priv_key = starfive_rsa_set_priv_key,
>> +	.max_size = starfive_rsa_max_size,
>> +	.init = starfive_rsa_init_tfm,
>> +	.exit = starfive_rsa_exit_tfm,
>> +	.base = {
>> +		.cra_name = "rsa",
>> +		.cra_driver_name = "starfive-rsa",
>> +		.cra_flags = CRYPTO_ALG_TYPE_AKCIPHER |
>> +			     CRYPTO_ALG_ASYNC |
> 
> Why did you set the ASYNC flag? Your implementation appears to
> be completely synchronous.
> 

I mixed this up with other modules, will remove this in next version.

Thanks,
Jia Jie


      reply	other threads:[~2023-05-25  1:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  7:57 [PATCH 0/2] crypto: starfive - Add RSA algo to drivers Jia Jie Ho
2023-05-16  7:57 ` [PATCH 1/2] crypto: starfive - Update hash module irq handling Jia Jie Ho
2023-05-16  7:57 ` [PATCH 2/2] crypto: starfive - Add RSA algo support Jia Jie Ho
2023-05-24  9:40   ` Herbert Xu
2023-05-25  1:56     ` Jia Jie Ho [this message]

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=29d515ec-83aa-c13e-b491-bc2ab7454012@starfivetech.com \
    --to=jiajie.ho@starfivetech.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox