From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>, Ori Kam <orika@nvidia.com>
Subject: RE: [PATCH 6/6] net/mlx5: add modify field action IPsec support
Date: Wed, 7 Feb 2024 11:45:14 +0000 [thread overview]
Message-ID: <IA1PR12MB83118F7AF999A11898C739FCA4452@IA1PR12MB8311.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240206121736.27391-6-viacheslavo@nvidia.com>
Hi Slava,
> + * Added HW steering support for modify field ``RTE_FLOW_FIELD_ESP_SPI`` flow action.
> + * Added HW steering support for modify field ``RTE_FLOW_FIELD_ESP_SEQ_NUM`` flow action.
> + * Added HW steering support for modify field ``RTE_FLOW_FIELD_ESP_PROTO`` flow action.
Could you please align this line with the rest of the items in that list, so that release notes generate properly?
Other than that, looks good to me.
Best regards,
Dariusz Sosnowski
next prev parent reply other threads:[~2024-02-07 11:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 12:17 [PATCH 1/6] ethdev: add modify IPv4 next protocol field Viacheslav Ovsiienko
2024-02-06 12:17 ` [PATCH 2/6] app/testpmd: add modify IPv4 next protocol command line Viacheslav Ovsiienko
2024-02-06 13:03 ` Ori Kam
2024-02-07 11:34 ` Dariusz Sosnowski
2024-02-06 12:17 ` [PATCH 3/6] net/mlx5: add modify IPv4 protocol implementation Viacheslav Ovsiienko
2024-02-07 11:36 ` Dariusz Sosnowski
2024-02-06 12:17 ` [PATCH 4/6] ethdev: add modify action support for IPsec fields Viacheslav Ovsiienko
2024-02-07 11:44 ` Dariusz Sosnowski
2024-02-06 12:17 ` [PATCH 5/6] app/testpmd: add modify ESP related fields command line Viacheslav Ovsiienko
2024-02-07 11:37 ` Dariusz Sosnowski
2024-02-06 12:17 ` [PATCH 6/6] net/mlx5: add modify field action IPsec support Viacheslav Ovsiienko
2024-02-07 11:45 ` Dariusz Sosnowski [this message]
2024-02-06 13:00 ` [PATCH 1/6] ethdev: add modify IPv4 next protocol field Ori Kam
2024-02-07 11:31 ` Dariusz Sosnowski
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=IA1PR12MB83118F7AF999A11898C739FCA4452@IA1PR12MB8311.namprd12.prod.outlook.com \
--to=dsosnowski@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=viacheslavo@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).