DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Ji, Kai" <kai.ji@intel.com>,
	"Karas, Krzysztof" <krzysztof.karas@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2] crypto/ipsec_mb: expect ENOTSUP
Date: Thu, 16 Mar 2023 18:46:49 +0000	[thread overview]
Message-ID: <CO6PR18MB4484BD04F1C38C71AD983593D8BC9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB3408A3AED0606003828419D081BE9@SN6PR11MB3408.namprd11.prod.outlook.com>

> Acked-by: Kai Ji <kai.ji@intel.com>
> 
> > Subject: [PATCH v2] crypto/ipsec_mb: expect ENOTSUP
> >
> > Commit b35848bc01f6 ("crypto/ipsec_mb: add multi-process IPC request
> > handler") is part of DPDK 22.11 release and it enforces usage of shared
> > config and multiprocess mode.
> >
> > DPDK is not required to be run with more than one process in general, so
> > instead of erroring out, catch the error and proceed with ipsec_mb
> > device creation normally.
> >
> > Fixes: b35848bc01f6 ("crypto/ipsec_mb: add multi-process IPC request
> > handler")
> > Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
> > ---
> > v2:
> >  * Modified patch title and added "Fixes:" note.
> >  * Restored original comparison "rte_errno == EEXIST".
> >
> >  .mailmap                                   | 1 +
> >  drivers/crypto/ipsec_mb/ipsec_mb_private.c | 2 +-
> >  2 files changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/.mailmap b/.mailmap
> > index a9f4f28fba..dad475b9d0 100644
> > --- a/.mailmap
> > +++ b/.mailmap
> > @@ -1583,3 +1583,4 @@ Ziye Yang <ziye.yang@intel.com>  Zoltan Kiss
> > <zoltan.kiss@schaman.hu> <zoltan.kiss@linaro.org>  Zorik Machulsky
> > <zorik@amazon.com>  Zyta Szpak <zyta@marvell.com> <zr@semihalf.com>
> > <zyta.szpak@semihalf.com>
> > +Krzysztof Karas <krzysztof.karas@intel.com>

Removed mailmap entry as it is already present + it should have been alphabetically sorted.

Applied to dpdk-next-crypto


      reply	other threads:[~2023-03-16 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 17:13 [PATCH] ipsec_mb: expect ENOTSUP in ipsec_mb_create() Krzysztof Karas
2023-02-27 18:26 ` [EXT] " Akhil Goyal
2023-02-28 23:24   ` Ji, Kai
2023-03-13 12:01 ` [PATCH v2] crypto/ipsec_mb: expect ENOTSUP Krzysztof Karas
2023-03-14 17:25   ` Ji, Kai
2023-03-16 18:46     ` 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=CO6PR18MB4484BD04F1C38C71AD983593D8BC9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=krzysztof.karas@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=thomas@monjalon.net \
    /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).