DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>,
	"fiona.trahe@intel.com" <fiona.trahe@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] doc: QAT support for AES-256 DOCSIS
Date: Sat, 9 May 2020 13:59:33 +0000	[thread overview]
Message-ID: <VI1PR04MB31682666B144526F115DC9E4E6A30@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1587646211-6039-1-git-send-email-mairtin.oloingsigh@intel.com>


> 
> Update QAT pmd to support AES-256 DOCSIS
> 
> Signed-off-by: Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
> ---
>  doc/guides/rel_notes/release_20_05.rst | 4 ++++
>  1 file changed, 4 insertions(+)
> 

This patch does not add the DOCSIS support in QAT.
The release note update should be the part of the patch which is adding the functionality.
If it was missed, then you should make this patch as a fix for the original patch
And give reference in the description.

> diff --git a/doc/guides/rel_notes/release_20_05.rst
> b/doc/guides/rel_notes/release_20_05.rst
> index 7f2049a0f..5e81c1964 100644
> --- a/doc/guides/rel_notes/release_20_05.rst
> +++ b/doc/guides/rel_notes/release_20_05.rst
> @@ -110,6 +110,10 @@ New Features
>    any checksum calculation was requested - in such case the code falls back to
>    fixed compression as before.
> 
> +* **Updated the QAT PMD.**
> +
> +  * Added AES-256 DOCSIS algorithm support to QAT PMD.
> +
>  * **Updated the turbo_sw bbdev PMD.**
> 
>    Supported large size code blocks which does not fit in one mbuf segment.
> --
> 2.12.3


      reply	other threads:[~2020-05-09 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 12:50 Mairtin o Loingsigh
2020-05-09 13:59 ` Akhil Goyal [this message]

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=VI1PR04MB31682666B144526F115DC9E4E6A30@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=mairtin.oloingsigh@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).