DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "kai.ji@intel.com" <kai.ji@intel.com>,
	"ciara.power@intel.com" <ciara.power@intel.com>
Subject: RE: [EXT] [PATCH] crypto/qat: add sm2 ecdsa
Date: Fri, 27 Oct 2023 19:24:43 +0000	[thread overview]
Message-ID: <CO6PR18MB448440C2C7E2BDFC3A4B458AD8DCA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230917154449.3509865-1-arkadiuszx.kusztal@intel.com>

> Added SM2 ECDSA feature to the Intel QuickAssist Technology
> symmetric crypto PMD.
> 
> Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> ---
The patch is not getting compiled on latest TOT. Please fix.
../drivers/crypto/qat/qat_asym.c: In function 'sm2_ecdsa_sign_set_input':
../drivers/crypto/qat/qat_asym.c:920:25: error: 'const struct rte_crypto_sm2_op_param' has no member named 'pkey'
  920 |  SET_PKE_LN(asym_op->sm2.pkey, qat_func_alignsize, 2);
      |                         ^
../drivers/crypto/qat/qat_asym.c:76:3: note: in definition of macro 'SET_PKE_LN'
   76 |   what.length, \
      |   ^~~~
../drivers/crypto/qat/qat_asym.c:920:25: error: 'const struct rte_crypto_sm2_op_param' has no member named 'pkey'
  920 |  SET_PKE_LN(asym_op->sm2.pkey, qat_func_alignsize, 2);
      |                         ^
../drivers/crypto/qat/qat_asym.c:77:3: note: in definition of macro 'SET_PKE_LN'
   77 |   what.data, \
      |   ^~~~

      parent reply	other threads:[~2023-10-27 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 15:44 Arkadiusz Kusztal
2023-10-23  9:28 ` Power, Ciara
2023-10-27 19:24 ` Akhil Goyal [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=CO6PR18MB448440C2C7E2BDFC3A4B458AD8DCA@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.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;
as well as URLs for NNTP newsgroup(s).