DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: fiona.trahe@intel.com, Adam Dybkowski <adamx.dybkowski@intel.com>
Cc: dev@dpdk.org, akhil.goyal@nxp.com, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v5 2/2] doc: update QAT PMD release notes
Date: Wed, 29 Jul 2020 00:16:56 +0200	[thread overview]
Message-ID: <4255215.b1rQD5ElBX@thomas> (raw)
In-Reply-To: <20200727101408.3539-3-adamx.dybkowski@intel.com>

27/07/2020 12:14, Adam Dybkowski:
> This patch updates 20.08 release notes inside
> the part that describe changes in Intel QuickAssist PMD.
> 
> Fixes: faa57df0b458 ("crypto/qat: support ChaCha20-Poly1305")
> Fixes: 9904ff684981 ("common/qat: improve multi-process handling")
> 
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> Acked-by: Fiona Trahe <fiona.trahe@intel.com>
> ---
>  doc/guides/rel_notes/release_20_08.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/doc/guides/rel_notes/release_20_08.rst b/doc/guides/rel_notes/release_20_08.rst
> index bb4a10053..dce18f84d 100644
> --- a/doc/guides/rel_notes/release_20_08.rst
> +++ b/doc/guides/rel_notes/release_20_08.rst
> @@ -196,9 +196,9 @@ New Features
>  
>  * **Updated the QuickAssist Technology (QAT) PMD.**
>  
> -  * Added support for lookaside protocol offload for DOCSIS through the
> -    ``rte_security`` API.
> -  * Added Chacha20-Poly1305 AEAD algorithm.
> +  * Added support for lookaside protocol offload in QAT crypto PMD
> +    for DOCSIS through the ``rte_security`` API.
> +  * Added Chacha20-Poly1305 AEAD algorithm in QAT crypto PMD.

I don't see the need for this patch.
Isn't it obvious that DOCSIS and ChachaPoly are related to crypto?
If you specify "QAT crypto PMD" or "QAT compress PMD"
in each item of QAT features, it will become not pleasant to read.



  reply	other threads:[~2020-07-28 22:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 12:29 [dpdk-dev] [PATCH] common/qat: support GEN2 device C34xx Adam Dybkowski
2020-07-13 11:09 ` [dpdk-dev] [PATCH v2 0/1] common/qat: support GEN2 QAT device 200xx Adam Dybkowski
2020-07-13 11:09   ` [dpdk-dev] [PATCH v2 1/1] " Adam Dybkowski
2020-07-13 15:27     ` Trahe, Fiona
2020-07-16 11:47   ` [dpdk-dev] [PATCH v3 0/2] " Adam Dybkowski
2020-07-16 11:47     ` [dpdk-dev] [PATCH v3 1/2] " Adam Dybkowski
2020-07-16 11:47     ` [dpdk-dev] [PATCH v3 2/2] doc: update QAT PMD release notes Adam Dybkowski
2020-07-16 16:54       ` Akhil Goyal
2020-07-22  8:07     ` [dpdk-dev] [PATCH v4 0/1] common/qat: support GEN2 QAT device 200xx Adam Dybkowski
2020-07-22  8:07       ` [dpdk-dev] [PATCH v4 1/1] " Adam Dybkowski
2020-07-22 11:05         ` Trahe, Fiona
2020-07-26 18:45         ` Akhil Goyal
2020-07-27 10:14       ` [dpdk-dev] [PATCH v5 0/2] " Adam Dybkowski
2020-07-27 10:14         ` [dpdk-dev] [PATCH v5 1/2] " Adam Dybkowski
2020-07-27 10:14         ` [dpdk-dev] [PATCH v5 2/2] doc: update QAT PMD release notes Adam Dybkowski
2020-07-28 22:16           ` Thomas Monjalon [this message]
2020-07-28 20:05         ` [dpdk-dev] [PATCH v5 0/2] common/qat: support GEN2 QAT device 200xx 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=4255215.b1rQD5ElBX@thomas \
    --to=thomas@monjalon.net \
    --cc=adamx.dybkowski@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=john.mcnamara@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).