From: Akhil Goyal <gakhil@marvell.com>
To: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>,
Kai Ji <kai.ji@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"ciara.power@intel.com" <ciara.power@intel.com>
Subject: RE: [EXT] [PATCH v3 1/2] crypto/ipsec_mb: bump minimum IPsec Multi-buffer version
Date: Thu, 22 Feb 2024 17:39:19 +0000 [thread overview]
Message-ID: <CO6PR18MB44842574738D9C23D557A7F4D8562@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240202140417.2399200-1-venkatx.sivaramakrishnan@intel.com>
> SW PMDs increment IPsec Multi-buffer version to 1.4.
> A minimum IPsec Multi-buffer version of 1.4 or greater is now required.
>
> Signed-off-by: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
> Acked-by: Ciara Power <ciara.power@intel.com>
> ---
> v2:
> - Removed unused macro in ipsec_mb_ops.c
> - set_gcm_job() modified correctly to keep multi_sgl_job line
> - Updated SW PMDs documentation for minimum IPSec Multi-buffer version
> - Updated commit message, and patch title.
Release notes update missing.
I think since you are bumping the version. It is worth notifying in release notes.
next prev parent reply other threads:[~2024-02-22 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 11:40 [PATCH v1] crypto/ipsec_mb: upgrade IPsec Multi-buffer to 1.4 Sivaramakrishnan Venkat
2024-01-23 11:42 ` Power, Ciara
2024-01-25 20:10 ` De Lara Guarch, Pablo
2024-01-30 14:24 ` [PATCH v2] crypto/ipsec_mb: bump minimum IPSec Multi-buffer version Sivaramakrishnan Venkat
2024-02-02 14:04 ` [PATCH v3 1/2] crypto/ipsec_mb: bump minimum IPsec " Sivaramakrishnan Venkat
2024-02-02 14:04 ` [PATCH v3 2/2] doc: remove outdated version details Sivaramakrishnan Venkat
2024-02-02 15:56 ` De Lara Guarch, Pablo
2024-02-02 15:56 ` [PATCH v3 1/2] crypto/ipsec_mb: bump minimum IPsec Multi-buffer version De Lara Guarch, Pablo
2024-02-22 17:39 ` Akhil Goyal [this message]
2024-02-23 12:29 ` [PATCH v4 " Sivaramakrishnan Venkat
2024-02-23 12:29 ` [PATCH v4 2/2] doc: remove outdated version details Sivaramakrishnan Venkat
2024-03-05 15:10 ` Wathsala Wathawana Vithanage
2024-03-05 15:13 ` [PATCH v4 1/2] crypto/ipsec_mb: bump minimum IPsec Multi-buffer version Wathsala Wathawana Vithanage
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=CO6PR18MB44842574738D9C23D557A7F4D8562@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=venkatx.sivaramakrishnan@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).