DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anoob Joseph <Anoob.Joseph@caviumnetworks.com>
To: Radu Nicolau <radu.nicolau@intel.com>, dev@dpdk.org
Cc: akhil.goyal@nxp.com, declan.doherty@intel.com,
	pablo.de.lara.guarch@intel.com
Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: print correct crypto name
Date: Mon, 12 Feb 2018 12:32:28 +0530	[thread overview]
Message-ID: <1e65bca1-641b-224b-f369-e85f88f08e01@caviumnetworks.com> (raw)
In-Reply-To: <1518172805-17461-1-git-send-email-radu.nicolau@intel.com>



On 09/02/18 16:10, Radu Nicolau wrote:
> When AES-256 was used aes-128 was printed in the console
>
> Fixes: fa9088849e12 ("examples/ipsec-secgw: support AES 256")
> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
Acked-by: Anoob Joseph <anoob.joseph@caviumnetworks.com>
> ---
>   examples/ipsec-secgw/sa.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/examples/ipsec-secgw/sa.c b/examples/ipsec-secgw/sa.c
> index 21239dd..d9dcc0e 100644
> --- a/examples/ipsec-secgw/sa.c
> +++ b/examples/ipsec-secgw/sa.c
> @@ -631,7 +631,8 @@ print_one_sa_rule(const struct ipsec_sa *sa, int inbound)
>   	printf("\tspi_%s(%3u):", inbound?"in":"out", sa->spi);
>   
>   	for (i = 0; i < RTE_DIM(cipher_algos); i++) {
> -		if (cipher_algos[i].algo == sa->cipher_algo) {
> +		if (cipher_algos[i].algo == sa->cipher_algo &&
> +				cipher_algos[i].key_len == sa->cipher_key_len) {
>   			printf("%s ", cipher_algos[i].keyword);
>   			break;
>   		}

  reply	other threads:[~2018-02-12  7:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 10:40 Radu Nicolau
2018-02-12  7:02 ` Anoob Joseph [this message]
2018-02-13 18:08   ` Thomas Monjalon

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=1e65bca1-641b-224b-f369-e85f88f08e01@caviumnetworks.com \
    --to=anoob.joseph@caviumnetworks.com \
    --cc=akhil.goyal@nxp.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=radu.nicolau@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).