patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Power, Ciara" <ciara.power@intel.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "anoobj@marvell.com" <anoobj@marvell.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] doc: fix invalid auth algo in cryptoperf app
Date: Tue, 11 Apr 2023 13:48:45 +0000	[thread overview]
Message-ID: <SN7PR11MB763944D06AA87804031BC41AE69A9@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230411130458.1134155-1-gakhil@marvell.com>



> -----Original Message-----
> From: Akhil Goyal <gakhil@marvell.com>
> Sent: Tuesday 11 April 2023 14:05
> To: dev@dpdk.org
> Cc: anoobj@marvell.com; Power, Ciara <ciara.power@intel.com>;
> stable@dpdk.org; Akhil Goyal <gakhil@marvell.com>
> Subject: [PATCH] doc: fix invalid auth algo in cryptoperf app
> 
> 3des-cbc is not an authentication algorithm, hence need to be removed.
> 
> Fixes: c6baca7adc94 ("doc: describe new performance test application")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Akhil Goyal <gakhil@marvell.com>
> ---
>  doc/guides/tools/cryptoperf.rst | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/doc/guides/tools/cryptoperf.rst b/doc/guides/tools/cryptoperf.rst
> index c77e253417..f30784674d 100644
> --- a/doc/guides/tools/cryptoperf.rst
> +++ b/doc/guides/tools/cryptoperf.rst
> @@ -232,7 +232,6 @@ The following are the application command-line
> options:
>          Set authentication algorithm name, where ``name`` is one
>          of the following::
> 
> -           3des-cbc
>             aes-cbc-mac
>             aes-cmac
>             aes-gmac
> --
> 2.25.1

Acked-by: Ciara Power <ciara.power@intel.com>

  reply	other threads:[~2023-04-11 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 13:04 Akhil Goyal
2023-04-11 13:48 ` Power, Ciara [this message]
2023-05-03  7:24   ` Akhil Goyal

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=SN7PR11MB763944D06AA87804031BC41AE69A9@SN7PR11MB7639.namprd11.prod.outlook.com \
    --to=ciara.power@intel.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.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).