All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>, <john.mcnamara@intel.com>
Cc: <dev@dpdk.org>, <declan.doherty@intel.com>,
	<pablo.de.lara.guarch@intel.com>, <hemant.agrawal@nxp.com>,
	<radu.nicolau@intel.com>, <borisp@mellanox.com>,
	<aviadye@mellanox.com>, <jerin.jacob@caviumnetworks.com>,
	<konstantin.ananyev@intel.com>
Subject: Re: [PATCH] doc: update release notes for rte_security
Date: Wed, 1 Nov 2017 11:50:55 +0530	[thread overview]
Message-ID: <380b3053-b903-032a-486e-b454b297afc9@nxp.com> (raw)
In-Reply-To: <1888299.Vl5Nplh0iF@xps>

Hi Thomas,
On 10/30/2017 7:52 PM, Thomas Monjalon wrote:
> 30/10/2017 13:27, Akhil Goyal:
>> Removed the deprication notice for ABI breakage and updated
>> release notes for rte_security.
>>
>> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
>> ---
>> +.. _security_library:
>> +
>>   Security Library
>>   ================
> [...]
>> +* **Added the Security Offload Library.**
>> +
>> +  Added an experimental library - rte_security. It provide security APIs for
>> +  protocols like IPSec using inline ipsec offload to ethernet device or full
>> +  protocol offload with lookaside crypto device.
>> +
>> +  See the :ref:`Security Library <Security_Library>` documentation in
>> +  the Programmers Guide document, for more information.
> 
> I think the reference to the programmer's guide is not so useful.
> I prefer avoiding it because it won't work in PDF format.
> 
> John, any opinion?
> 

I added this reference as there was another one in the release notes 
already for membership library.

I will remove reference to security library, if it is not required. 
Please let me know.

Thanks,
Akhil

  reply	other threads:[~2017-11-01  6:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 12:27 [PATCH] doc: update release notes for rte_security Akhil Goyal
2017-10-30 14:22 ` Thomas Monjalon
2017-11-01  6:20   ` Akhil Goyal [this message]
2017-11-02 16:36     ` Mcnamara, John
2017-11-07  6:44 ` [PATCH v2] " Akhil Goyal
2017-11-08  1:07   ` 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=380b3053-b903-032a-486e-b454b297afc9@nxp.com \
    --to=akhil.goyal@nxp.com \
    --cc=aviadye@mellanox.com \
    --cc=borisp@mellanox.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=john.mcnamara@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=radu.nicolau@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.