DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Fan" <fanzhang.oss@gmail.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	dev@dpdk.org, kai.ji@intel.com, g.singh@nxp.com,
	hemant.agrawal@nxp.com, pablo.de.lara.guarch@intel.com
Cc: stable@dpdk.org
Subject: Re: [PATCH 1/6] crypto/qat: fix sym device prototype
Date: Fri, 9 Jun 2023 15:03:25 +0100	[thread overview]
Message-ID: <cd2cd3e1-cfc5-a8f9-2e2a-204d559a70c3@gmail.com> (raw)
In-Reply-To: <20230609135450.476983-2-maxime.coquelin@redhat.com>


On 6/9/2023 2:54 PM, Maxime Coquelin wrote:
> qat_dev_cmd_param parameter of qat_sym_dev_create() was
> wrongly marked as unused, this patch fixes it.
>
> Fixes: fb3b9f492205 ("crypto/qat: rework burst data path")
> Cc: stable@dpdk.org
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
>   drivers/crypto/qat/qat_sym.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/qat/qat_sym.c b/drivers/crypto/qat/qat_sym.c
> index 08e92191a3..2450f042c8 100644
> --- a/drivers/crypto/qat/qat_sym.c
> +++ b/drivers/crypto/qat/qat_sym.c
> @@ -179,7 +179,7 @@ qat_sym_dequeue_burst(void *qp, struct rte_crypto_op **ops,
>   
>   int
>   qat_sym_dev_create(struct qat_pci_device *qat_pci_dev,
> -		struct qat_dev_cmd_param *qat_dev_cmd_param __rte_unused)
> +		struct qat_dev_cmd_param *qat_dev_cmd_param)
>   {
>   	int i = 0, ret = 0;
>   	uint16_t slice_map = 0;

Acked-by: Fan Zhang <fanzhang.oss@gmail.com>


  reply	other threads:[~2023-06-09 14:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 13:54 [PATCH 0/6] Trivial crypto PMDs cleanup Maxime Coquelin
2023-06-09 13:54 ` [PATCH 1/6] crypto/qat: fix sym device prototype Maxime Coquelin
2023-06-09 14:03   ` Zhang, Fan [this message]
2023-06-09 15:40     ` Tyler Retzlaff
2023-06-09 13:54 ` [PATCH 2/6] crypto/qat: remove security lib presence checks Maxime Coquelin
2023-06-09 13:54 ` [PATCH 3/6] crypto/dpaa2_sec: " Maxime Coquelin
2023-06-09 15:04   ` Hemant Agrawal
2023-06-09 13:54 ` [PATCH 4/6] crypto/dpaa_sec: " Maxime Coquelin
2023-06-09 15:05   ` Hemant Agrawal
2023-06-09 13:54 ` [PATCH 5/6] crypto/ipsec_mb: " Maxime Coquelin
2023-06-09 13:54 ` [PATCH 6/6] crypto/qat: remove useless log level checks Maxime Coquelin
2023-06-09 14:02   ` Zhang, Fan
2023-06-14 18:17 ` [EXT] [PATCH 0/6] Trivial crypto PMDs cleanup Akhil Goyal
2023-06-20  6:49   ` Akhil Goyal
2023-06-20  7:54     ` Maxime Coquelin

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=cd2cd3e1-cfc5-a8f9-2e2a-204d559a70c3@gmail.com \
    --to=fanzhang.oss@gmail.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=kai.ji@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).