DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Liron Himi <lironh@marvell.com>,
	Michael Shamis <michaelsh@marvell.com>,
	Akhil Goyal <gakhil@marvell.com>
Cc: Dana Vardi <danat@marvell.com>,
	dev@dpdk.org, "dev@dpdk.org" <dev@dpdk.org>,
	Dana Vardi <danat@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2] crypto/mvsam: IPSec full offload support
Date: Wed, 21 Jul 2021 14:48:05 +0200	[thread overview]
Message-ID: <232412235.Au2DmXXTsM@thomas> (raw)
In-Reply-To: <CO6PR18MB4484D25D43D9726395FA9CBAD8E29@CO6PR18MB4484.namprd18.prod.outlook.com>

The correct wording is "IPsec"
and it is flagged by devtools/check-git-log.sh

20/07/2021 22:49, Akhil Goyal:
> > From: Michael Shamis <michaelsh@marvell.com>
> > 
> > This patch provides the support for IPSec protocol
> > offload to the hardware.
> > Following security operations are added:
> > - session_create
> > - session_destroy
> > - capabilities_get
> > 
> > Signed-off-by: Michael Shamis <michaelsh@marvell.com>
> > Reviewed-by: Liron Himi <lironh@marvell.com>
> > Tested-by: Liron Himi <lironh@marvell.com>
> > ---
> Applied to dpdk-next-crypto

A checkpatch warning was ignored:

Warning in drivers/crypto/mvsam/rte_mrvl_pmd.c:
Declaring a variable inside for()





  reply	other threads:[~2021-07-21 12:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01  6:57 [dpdk-dev] [PATCH] " danat
2021-07-11  6:55 ` [dpdk-dev] [PATCH v2] " danat
2021-07-20 20:49   ` Akhil Goyal
2021-07-21 12:48     ` Thomas Monjalon [this message]
2021-07-21 13:01       ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-21 13:14         ` Akhil Goyal
2021-07-21 13:54           ` Thomas Monjalon
2021-07-22  7:40             ` 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=232412235.Au2DmXXTsM@thomas \
    --to=thomas@monjalon.net \
    --cc=danat@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=lironh@marvell.com \
    --cc=michaelsh@marvell.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).