From: Akhil Goyal <gakhil@marvell.com>
To: "Ji, Kai" <kai.ji@intel.com>
Cc: "Power, Ciara" <ciara.power@intel.com>,
"Dooley, Brian" <brian.dooley@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: RE: [PATCH v4] doc: support IPsec Multi-buffer lib v1.3
Date: Tue, 15 Nov 2022 09:24:55 +0000 [thread overview]
Message-ID: <CO6PR18MB448457B3F9AD22ECCBF9FC9FD8049@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB3408AB65C69C4B43C09A91F181059@SN6PR11MB3408.namprd11.prod.outlook.com>
> Hi Akhil,
>
> I remember you have a comment in earlier version of this patch about to
> include this ipsec mb v1.3 release doc update into release notes.
> I have review the release_22_11.rst, but I'm not sure the best section to capture
> this info , any recommendations ?
>
It can be added as a bullet in
240
241 * **Updated ipsec_mb crypto driver.**
242
243 Added SNOW-3G and ZUC support for ARM platform.
244
next prev parent reply other threads:[~2022-11-15 9:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 18:33 [PATCH] " Pablo de Lara
2022-11-09 18:39 ` [PATCH v2] " Pablo de Lara
2022-11-10 9:38 ` [EXT] " Akhil Goyal
2022-11-10 10:43 ` Power, Ciara
2022-11-10 11:07 ` [PATCH v3] " Pablo de Lara
2022-11-10 11:17 ` Dooley, Brian
2022-11-10 11:39 ` Ji, Kai
2022-11-11 16:24 ` De Lara Guarch, Pablo
2022-11-10 16:44 ` Zhang, Fan
2022-11-12 11:26 ` [PATCH v4] " Pablo de Lara
2022-11-14 23:34 ` Ji, Kai
2022-11-15 9:24 ` Akhil Goyal [this message]
2022-11-15 17:11 ` [dpdk-dev v5] " Kai Ji
2022-11-15 20:17 ` Zhang, Fan
2022-11-16 12:06 ` [dpdk-dev v6] " Kai Ji
2022-11-17 12:16 ` Kai Ji
2022-11-21 6:57 ` [EXT] " Akhil Goyal
2022-11-21 10:57 ` Zhang, Fan
2022-11-21 11:35 ` Akhil Goyal
2022-11-21 13:52 ` Zhang, Fan
2022-11-21 16:35 ` [dpdk-dev v7] " Kai Ji
2022-11-22 11:57 ` 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=CO6PR18MB448457B3F9AD22ECCBF9FC9FD8049@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=brian.dooley@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@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).