From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Dongdong Liu <liudongdong3@huawei.com>,
dev@dpdk.org, thomas@monjalon.net, andrew.rybchenko@oktetlabs.ru
Cc: stable@dpdk.org, haijie1@huawei.com
Subject: Re: [PATCH 0/7] add setting and querying of LLRS FEC mode
Date: Thu, 1 Jun 2023 09:30:57 +0100 [thread overview]
Message-ID: <3f5424a6-6136-0563-2d68-e43e635df456@amd.com> (raw)
In-Reply-To: <20230408022740.14522-1-liudongdong3@huawei.com>
On 4/8/2023 3:27 AM, Dongdong Liu wrote:
> This patchset include some bugfixes for hns3 fec and add setting and
> querying of LLRS FEC mode.
>
> Jie Hai (7):
> net/hns3: fix fec mode for 200G ports
> net/hns3: fix fec mode check error
> net/hns3: fix missing FEC capability
> ethdev: introduce low latency RS FEC
> app/testpmd: add setting and querying of LLRS FEC mode
> net/hns3: add LLRS FEC mode support for 200G ports
> net/hns3: support getting current FEC capability from firmware
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-06-01 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 2:27 Dongdong Liu
2023-04-08 2:27 ` [PATCH 1/7] net/hns3: fix fec mode for 200G ports Dongdong Liu
2023-04-08 2:27 ` [PATCH 2/7] net/hns3: fix fec mode check error Dongdong Liu
2023-04-08 2:27 ` [PATCH 3/7] net/hns3: fix missing FEC capability Dongdong Liu
2023-04-08 2:27 ` [PATCH 4/7] ethdev: introduce low latency RS FEC Dongdong Liu
2023-06-01 8:30 ` Ferruh Yigit
2023-04-08 2:27 ` [PATCH 5/7] app/testpmd: add setting and querying of LLRS FEC mode Dongdong Liu
2023-04-28 6:50 ` Singh, Aman Deep
2023-04-08 2:27 ` [PATCH 6/7] net/hns3: add LLRS FEC mode support for 200G ports Dongdong Liu
2023-04-08 2:27 ` [PATCH 7/7] net/hns3: support getting current FEC capability from firmware Dongdong Liu
2023-06-01 8:30 ` Ferruh Yigit [this message]
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=3f5424a6-6136-0563-2d68-e43e635df456@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=haijie1@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).