mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: yumeng <yumeng18@huawei.com>
To: Daniele Alessandrelli <daniele.alessandrelli@intel.com>
Cc: <davem@davemloft.net>, <linux-crypto@vger.kernel.org>,
	<xuzaibo@huawei.com>, <wangzhou1@hisilicon.com>,
	<linux-kernel@vger.kernel.org>,
	Mark Gross <mgross@linux.intel.com>,
	"Prabhjot Khurana" <prabhjot.khurana@intel.com>,
	Elena Reshetova <elena.reshetova@intel.com>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH v5 3/5] crypto: expose elliptic curve parameters as Crypto APIs
Date: Mon, 4 Jan 2021 17:36:33 +0800	[thread overview]
Message-ID: <a260ceec-e3ca-8fbd-e80e-f08ddc2029a4@huawei.com> (raw)
In-Reply-To: <20210102212929.GA1996@gondor.apana.org.au>



在 2021/1/3 5:29, Herbert Xu 写道:
> On Thu, Dec 24, 2020 at 02:08:25PM +0800, Meng Yu wrote:
>> Move elliptic curves definition to 'include/crypto/ecc_curve_defs.h',
>> so all can use it,
>>
>> Signed-off-by: Meng Yu <yumeng18@huawei.com>
>> Reviewed-by: Zaibo Xu <xuzaibo@huawei.com>
>> ---
>>   crypto/ecc.c                    |  1 -
>>   crypto/ecc.h                    | 37 +----------------
>>   crypto/ecc_curve_defs.h         | 57 -------------------------
>>   crypto/ecrdsa_defs.h            |  2 +-
>>   include/crypto/ecc_curve_defs.h | 92 +++++++++++++++++++++++++++++++++++++++++
>>   5 files changed, 95 insertions(+), 94 deletions(-)
>>   delete mode 100644 crypto/ecc_curve_defs.h
>>   create mode 100644 include/crypto/ecc_curve_defs.h
> 
> This conflicts with
> 
> https://patchwork.kernel.org/project/linux-crypto/patch/20201217172101.381772-3-daniele.alessandrelli@linux.intel.com/
> 
> Please discuss with each other on how you would like to proceed.
> 
> Thanks,
> 

hello, Daniele,

In my patch, I move elliptic curves definition to 
'include/crypto/ecc_curve_defs.h',
which include the P-384 curve you need, and you can easily import it to 
your driver.

And if you include 'crypto/ecc_curve_defs.h', 
'drivers/crypto/keembay/ocs-ecc-curve-defs.h'
is not needed.

Could you think about it, to rely on my patchset?

  reply	other threads:[~2021-01-04  9:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  6:08 [PATCH v5 0/5] add ECDH and CURVE25519 algorithms support for Kunpeng 930 Meng Yu
2020-12-24  6:08 ` [PATCH v5 1/5] crypto: hisilicon/hpre - add some updates to adapt to " Meng Yu
2020-12-24  6:08 ` [PATCH v5 2/5] crypto: hisilicon/hpre - add algorithm type Meng Yu
2020-12-24  6:08 ` [PATCH v5 3/5] crypto: expose elliptic curve parameters as Crypto APIs Meng Yu
2021-01-02 21:29   ` Herbert Xu
2021-01-04  9:36     ` yumeng [this message]
2021-01-04 11:36       ` Alessandrelli, Daniele
2021-01-04 12:49         ` Herbert Xu
2020-12-24  6:08 ` [PATCH v5 4/5] crypto: hisilicon/hpre - add 'ECDH' algorithm Meng Yu
2020-12-24  6:08 ` [PATCH v5 5/5] crypto: hisilicon/hpre - add 'CURVE25519' algorithm Meng Yu

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=a260ceec-e3ca-8fbd-e80e-f08ddc2029a4@huawei.com \
    --to=yumeng18@huawei.com \
    --cc=daniele.alessandrelli@intel.com \
    --cc=davem@davemloft.net \
    --cc=elena.reshetova@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --cc=prabhjot.khurana@intel.com \
    --cc=wangzhou1@hisilicon.com \
    --cc=xuzaibo@huawei.com \
    /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®