DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Tomasz Jozwiak <tomaszx.jozwiak@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 "fiona.trahe@intel.com" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add description to release note
Date: Tue, 30 Apr 2019 07:12:44 +0000	[thread overview]
Message-ID: <VI1PR04MB4893F9A8B509342D6AF72876E63A0@VI1PR04MB4893.eurprd04.prod.outlook.com> (raw)

Hi Tomasz,

> 
> 
> Added description about compression QAT PMD improvement
> 
> Signed-off-by: Tomasz Jozwiak <tomaszx.jozwiak@intel.com>
> ---
>  doc/guides/rel_notes/release_19_05.rst | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/release_19_05.rst
> b/doc/guides/rel_notes/release_19_05.rst
> index b0928a6..624625f 100644
> --- a/doc/guides/rel_notes/release_19_05.rst
> +++ b/doc/guides/rel_notes/release_19_05.rst
> @@ -146,6 +146,9 @@ New Features
> 
>    Added support for AES-XTS with 128 and 256 bit AES keys.
> 
> +  Simplify and make more robust QAT compressdev PMD's handling of SGLs with
> +  more than 16 segments.
> +
>  * **Updated AESNI-MB PMD.**
> 
>    Added support for out-of-place operations.


This patch is not clear neither from the subject nor from the release note update.
The description that you added here is for QAT compress PMD but it is added in description of QAT crypto PMD.

You should make a separate entry for QAT compress PMD and update the existing one with crypto PMD

Also the patch subject should be "doc: update release note for QAT compress PMD" or something more descriptive.

Thanks,
Akhil

             reply	other threads:[~2019-04-30  7:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30  7:12 Akhil Goyal [this message]
2019-04-30  7:12 ` Akhil Goyal
  -- strict thread matches above, loose matches on Subject: below --
2019-04-18  7:58 Tomasz Jozwiak
2019-04-18  7:58 ` Tomasz Jozwiak
2019-04-18 11:46 ` Trahe, Fiona
2019-04-18 11:46   ` Trahe, Fiona

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=VI1PR04MB4893F9A8B509342D6AF72876E63A0@VI1PR04MB4893.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=tomaszx.jozwiak@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).