All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Raja Zidane <rzidane@nvidia.com>
Cc: dev@dpdk.org, Matan Azrad <matan@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH V2] crypto/mlx5: support BF2 and ConnectX6-DX devices
Date: Sun, 07 Nov 2021 18:44:40 +0100	[thread overview]
Message-ID: <3179376.2RoD1SifGA@thomas> (raw)
In-Reply-To: <20211107172957.3962-1-rzidane@nvidia.com>

07/11/2021 18:29, Raja Zidane:
> --- a/doc/guides/rel_notes/release_21_11.rst
> +++ b/doc/guides/rel_notes/release_21_11.rst
> @@ -401,6 +401,10 @@ New Features
>    overruns in C/C++ programs, and other similar errors, as well as
>    printing out detailed debug information whenever an error is detected.
>  
> +* **Updated mlx5 crypto driver.**
> +
> +  * Added support for BF2.
> +  * Added support for CX6DX.

I you don't know where to put something in a list,
choosing to put at the end is almost always a bad decision.

In the case of the release notes, the order is described at the beginning.
And in this particular case, there is already a matching section:

* **Updated Mellanox mlx5 crypto driver.**

  * Added Windows support.




  reply	other threads:[~2021-11-07 17:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07 16:22 [dpdk-dev] [PATCH] crypto/mlx5: support BF2 and ConnectX6-DX devices Raja Zidane
2021-11-07 16:26 ` Raja Zidane
2021-11-07 17:29   ` [dpdk-dev] [PATCH V2] " Raja Zidane
2021-11-07 17:44     ` Thomas Monjalon [this message]
2021-11-07 19:03     ` Tal Shnaiderman
2021-11-08 13:18     ` [dpdk-dev] [PATCH V3] " Raja Zidane
2021-11-08 14:03       ` Tal Shnaiderman
2021-11-10 12:27       ` [dpdk-dev] [PATCH V4] " Raja Zidane
2021-11-10 12:47         ` Tal Shnaiderman
2021-11-11 11:11         ` [EXT] " Akhil Goyal
2021-11-11 13:51         ` [PATCH V5] " Raja Zidane
2021-11-12  8:43           ` [EXT] " 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=3179376.2RoD1SifGA@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rzidane@nvidia.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 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.