DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: release note for the IPsec library
Date: Fri, 26 Jul 2019 10:49:18 +0000	[thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C260DD4AE7@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <VE1PR04MB663943FA8262D88C55C950FEE6C00@VE1PR04MB6639.eurprd04.prod.outlook.com>

Hi Akhil,

> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Friday, July 26, 2019 11:27 AM
> To: Iremonger, Bernard <bernard.iremonger@intel.com>; dev@dpdk.org;
> Ananyev, Konstantin <konstantin.ananyev@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>
> Subject: RE: [PATCH v3] doc: release note for the IPsec library
> 
> Hi Bernard,
> 
> >
> > Update release notes for changes to the IPsec library.
> >
> > Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
> > ---
> > changes in v3:
> > revised content
> >
> >  doc/guides/rel_notes/release_19_08.rst | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/release_19_08.rst
> > b/doc/guides/rel_notes/release_19_08.rst
> > index c9bd3ce..7737ebe 100644
> > --- a/doc/guides/rel_notes/release_19_08.rst
> > +++ b/doc/guides/rel_notes/release_19_08.rst
> > @@ -224,6 +224,14 @@ New Features
> >
> >    Added multiple cores feature to compression perf tool application.
> >
> > +* **Updated the IPsec library.**
> > +
> > +  Added the following functionality to ``librte_ipsec``.
> > +
> > +  * Added support for transport mode with IPv6 extension headers.
> > +
> > +  * Added support for packets that consist of multiple segments.
> > +
> >
> 
> Ipsec library changes are already there in the release note.
> Could you please consolidate all changes in ipsec lib in a single bullet.
> 
> Also the ipsec-secgw application changes can also be there in that single
> bullet. As the features are same for ipsec lib and ipsec application.
> 
> So I would say, we can combine the two commits in a single bullet already
> there in the release note for header reconstruction.
> http://patches.dpdk.org/patch/57122/
> http://patches.dpdk.org/patch/57124/
> 
> 
> -Akhil

I will update existing bullet with info in patches 57122 and 57124.

Regards,

Bernard.


  reply	other threads:[~2019-07-26 10:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25  9:59 [dpdk-dev] [PATCH] " Bernard Iremonger
2019-07-25 12:58 ` [dpdk-dev] [PATCH v2] " Bernard Iremonger
2019-07-25 14:39   ` [dpdk-dev] [PATCH v3] " Bernard Iremonger
2019-07-25 14:52     ` Ananyev, Konstantin
2019-07-26 10:27     ` Akhil Goyal
2019-07-26 10:49       ` Iremonger, Bernard [this message]
2019-07-26 11:57     ` [dpdk-dev] [PATCH v4] doc: release note for the IPsec library and application Bernard Iremonger
2019-07-26 12:36       ` Akhil Goyal
2019-07-26 13:17         ` Iremonger, Bernard
2019-07-26 13:42       ` [dpdk-dev] [PATCH v5] " Bernard Iremonger
2019-07-26 13:44         ` Akhil Goyal
2019-07-26 13:54           ` 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=8CEF83825BEC744B83065625E567D7C260DD4AE7@IRSMSX108.ger.corp.intel.com \
    --to=bernard.iremonger@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=konstantin.ananyev@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).