From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Sean Zhang <xiazhang@nvidia.com>, Matan Azrad <matan@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Cc: <dev@dpdk.org>
Subject: Re: [v1 0/4] Add support for modifying ECN in IPv4/IPv6 header
Date: Thu, 2 Jun 2022 12:44:42 +0100 [thread overview]
Message-ID: <ca571069-0791-781c-08b3-f26993f44a28@xilinx.com> (raw)
In-Reply-To: <1b9cd828-3f3c-0de0-d8dd-9af169489ce0@xilinx.com>
On 6/1/2022 7:51 PM, Ferruh Yigit wrote:
> On 4/2/2022 8:11 AM, Sean Zhang wrote:
>> This patch set adds support for modifying ECN fields in IPv4/IPv6
>> header, and also adds support for modify_filed action in meter.
>>
>> Jiawei Wang (1):
>> ethdev: add IPv4/IPv6 ECN header rewrite action
>>
>> Sean Zhang (3):
>> common/mlx5: add modify ECN capability check
>> net/mlx5: add support to modify ECN field
>> net/mlx5: add modify field support in meter
>>
>
> To be able to merge it as set, mlx5 driver patches requires driver
> maintainer's ack/review.
>
> @Matan, @Slava, can you please check them?
Hi Sean,
ethdev patch is merged to have it in -rc1, driver patches can be handled
separately.
next prev parent reply other threads:[~2022-06-02 11:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 7:11 Sean Zhang
2022-04-02 7:11 ` [v1 1/4] ethdev: add IPv4/IPv6 ECN header rewrite action Sean Zhang
2022-06-01 18:51 ` Ferruh Yigit
2022-06-02 5:48 ` Ori Kam
2022-06-02 11:44 ` Ferruh Yigit
2022-04-02 7:11 ` [v1 2/4] common/mlx5: add modify ECN capability check Sean Zhang
2022-06-06 8:05 ` Slava Ovsiienko
2022-04-02 7:11 ` [v1 3/4] net/mlx5: add support to modify ECN field Sean Zhang
2022-06-06 7:17 ` Slava Ovsiienko
2022-04-02 7:11 ` [v1 4/4] net/mlx5: add modify field support in meter Sean Zhang
2022-06-06 7:18 ` Slava Ovsiienko
2022-06-01 18:51 ` [v1 0/4] Add support for modifying ECN in IPv4/IPv6 header Ferruh Yigit
2022-06-02 11:44 ` Ferruh Yigit [this message]
2022-06-02 13:13 ` Sean Zhang (Networking SW)
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=ca571069-0791-781c-08b3-f26993f44a28@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=viacheslavo@nvidia.com \
--cc=xiazhang@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).