From: Thomas Monjalon <thomas@monjalon.net>
To: Francis Kelly <fkelly@nvidia.com>, Ady Agbarih <aagbarih@nvidia.com>
Cc: dev@dpdk.org, JAMES HUNTER <jamhunter@nvidia.com>,
Ori Kam <orika@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH 10/10] doc: updated release notes and mlx5 file
Date: Wed, 03 Nov 2021 23:13:47 +0100 [thread overview]
Message-ID: <1700915.6gu4zaQKso@thomas> (raw)
In-Reply-To: <DM8PR12MB5400842FDA996A4C3D36E199D6829@DM8PR12MB5400.namprd12.prod.outlook.com>
A cover letter is missing for this series.
> > Provided further description within documentation regarding
> > the RXP to CRSpace changes.
This patch should be squashed with the relevant code change.
> > --- a/doc/guides/rel_notes/release_21_11.rst
> > +++ b/doc/guides/rel_notes/release_21_11.rst
> > +* **Updated Mellanox mlx5 driver.**
regex should be mentioned
> > +
> > + * Added support for new ROF file format.
>
> Acked-by: Ori Kam <orika@nvidia.com>
I had to rebase the series after the MR changes.
The patch 8 is fixing the patch 2.
We should not do that in a series, so I squashed them,
updating explanations and authors.
With above fixes, applied, thanks.
next prev parent reply other threads:[~2021-11-03 22:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 15:45 [dpdk-dev] [PATCH 01/10] common/mlx5: update PRM definitions for regex availability Francis Kelly
2021-10-22 15:45 ` [dpdk-dev] [PATCH 02/10] regex/mlx5: add cleanup code Francis Kelly
2021-10-22 15:45 ` [dpdk-dev] [PATCH 03/10] common/mlx5: update regex DevX commands Francis Kelly
2021-10-24 13:39 ` Ori Kam
2021-10-22 15:45 ` [dpdk-dev] [PATCH 04/10] regex/mlx5: remove regexp register read/write Francis Kelly
2021-10-24 13:40 ` Ori Kam
2021-10-22 15:45 ` [dpdk-dev] [PATCH 05/10] regex/mlx5: move RXP to CrSpace Francis Kelly
2021-10-24 13:41 ` Ori Kam
2021-10-22 15:45 ` [dpdk-dev] [PATCH 06/10] regex/mlx5: remove start/stop engine API Francis Kelly
2021-10-22 15:45 ` [dpdk-dev] [PATCH 07/10] regex/mlx5: removed redundant rxp csr file Francis Kelly
2021-10-24 13:42 ` Ori Kam
2021-10-22 15:45 ` [dpdk-dev] [PATCH 08/10] regex/mlx5: fix uninitialized QP destroy Francis Kelly
2021-10-24 13:42 ` Ori Kam
2021-10-22 15:45 ` [dpdk-dev] [PATCH 09/10] regex/mlx5: prevent QP double setup Francis Kelly
2021-10-24 13:43 ` Ori Kam
2021-10-22 15:46 ` [dpdk-dev] [PATCH 10/10] doc: updated release notes and mlx5 file Francis Kelly
2021-10-24 13:43 ` Ori Kam
2021-11-03 22:13 ` Thomas Monjalon [this message]
2021-10-24 13:38 ` [dpdk-dev] [PATCH 01/10] common/mlx5: update PRM definitions for regex availability Ori Kam
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=1700915.6gu4zaQKso@thomas \
--to=thomas@monjalon.net \
--cc=aagbarih@nvidia.com \
--cc=dev@dpdk.org \
--cc=fkelly@nvidia.com \
--cc=jamhunter@nvidia.com \
--cc=orika@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 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).