From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Denis Pryazhennikov <denis.pryazhennikov@arknetworks.am>, dev@dpdk.org
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [PATCH v2 0/3] net/sfc: support FEC feature
Date: Tue, 20 Jun 2023 12:47:52 +0100 [thread overview]
Message-ID: <1d4a8b26-10a5-1858-40f9-ade62e39b203@amd.com> (raw)
In-Reply-To: <20230615083847.75590-1-denis.pryazhennikov@arknetworks.am>
On 6/15/2023 9:38 AM, Denis Pryazhennikov wrote:
> This patch series adds setting and querying of Forward error
> correction (FEC). AUTO, BASER and RS modes are supported
> by EF10/EF100 hardware. LLRS mode is not supported.
>
> Changes in v2:
> * Applied review notes in [2/3] and [3/3];
> * Added a check for the supported by a device FEC modes
> in sfc_fec_get_capa_speed_to_fec();
> * Fixed error handling.
>
> Denis Pryazhennikov (3):
> net/sfc: split link update function
> common/sfc_efx/base: add FEC related macros
> net/sfc: support FEC feature
>
2/3 squashed into 3/3,
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-06-20 11:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 22:23 [PATCH " Denis Pryazhennikov
2023-06-01 22:23 ` [PATCH 1/3] net/sfc: split link update function Denis Pryazhennikov
2023-06-02 8:52 ` Andrew Rybchenko
2023-06-20 11:25 ` Ferruh Yigit
2023-06-20 11:43 ` Andrew Rybchenko
2023-06-01 22:23 ` [PATCH 2/3] common/sfc_efx/base: add FEC related macros Denis Pryazhennikov
2023-06-02 8:53 ` Andrew Rybchenko
2023-06-01 22:23 ` [PATCH 3/3] net/sfc: support FEC feature Denis Pryazhennikov
2023-06-02 9:09 ` Andrew Rybchenko
2023-06-15 8:38 ` [PATCH v2 0/3] " Denis Pryazhennikov
2023-06-15 8:38 ` [PATCH v2 1/3] net/sfc: split link update function Denis Pryazhennikov
2023-06-15 8:38 ` [PATCH v2 2/3] common/sfc_efx/base: add FEC related macros Denis Pryazhennikov
2023-06-20 11:34 ` Ferruh Yigit
2023-06-15 8:38 ` [PATCH v2 3/3] net/sfc: support FEC feature Denis Pryazhennikov
2023-06-19 9:39 ` Andrew Rybchenko
2023-06-20 11:33 ` Ferruh Yigit
2023-06-20 11:47 ` 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=1d4a8b26-10a5-1858-40f9-ade62e39b203@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=denis.pryazhennikov@arknetworks.am \
--cc=dev@dpdk.org \
/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).