From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>, dev@dpdk.org
Cc: kaara.satwik@chelsio.com
Subject: Re: [dpdk-dev] [PATCH 0/3] net/cxgbe: rework link config and add FEC support
Date: Fri, 15 Jan 2021 15:02:47 +0000 [thread overview]
Message-ID: <0cc56165-161c-38df-14d3-eac5dbb502a7@intel.com> (raw)
In-Reply-To: <cover.1608504560.git.rahul.lakkireddy@chelsio.com>
On 12/20/2020 10:47 PM, Rahul Lakkireddy wrote:
> This series of patches rework link handling and add support to
> configure Forward Error Correction (FEC) capability.
>
> Patch 1 removes legacy 16-bit link capabilities infrastructure
> and always enables 32-bit link capabilities in firmware.
>
> Patch 2 simplifies link handling in preparation for FEC support.
>
> Patch 3 adds support to configure link FEC when supported.
>
> Thanks,
> Rahul
>
> Karra Satwik (3):
> net/cxgbe: remove legacy 16-bit link capabilities
> net/cxgbe: rework and simplify link handling code
> net/cxgbe: implement ethdev ops to configure link FEC
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-01-15 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 22:47 Rahul Lakkireddy
2020-12-20 22:47 ` [dpdk-dev] [PATCH 1/3] net/cxgbe: remove legacy 16-bit link capabilities Rahul Lakkireddy
2020-12-20 22:47 ` [dpdk-dev] [PATCH 2/3] net/cxgbe: rework and simplify link handling code Rahul Lakkireddy
2020-12-20 22:47 ` [dpdk-dev] [PATCH 3/3] net/cxgbe: implement ethdev ops to configure link FEC Rahul Lakkireddy
2021-01-15 15:02 ` 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=0cc56165-161c-38df-14d3-eac5dbb502a7@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=kaara.satwik@chelsio.com \
--cc=rahul.lakkireddy@chelsio.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).