From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jiawen Wu <jiawenwu@trustnetic.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4 0/6] txgbe backplane AN training
Date: Mon, 29 Mar 2021 16:51:12 +0100 [thread overview]
Message-ID: <a05f2e08-a69c-a5da-9a4f-b8204e74c9ca@intel.com> (raw)
In-Reply-To: <20210329031724.1468339-1-jiawenwu@trustnetic.com>
On 3/29/2021 4:17 AM, Jiawen Wu wrote:
> This series update link process for backplane NICs.
> And support to control AN training.
>
> v4:
> - Convert BP_LOG to dynamic log.
> v3:
> - Add devargs gradually in the patches they are used.
> - Update 21.05 relaese notes.
> v2:
> - Convert compile time flags to runtime options
> - Move firmware version get operation to base code
> - Fix minor bugs
>
> Jiawen Wu (6):
> net/txgbe: update device ID
> net/txgbe: move firmware version get function to base code
> net/txgbe: update link setup process of backplane NICs
> net/txgbe/base: support to handle backplane AN73 flow
> net/txgbe: handle AN interrupt and link update
> net/txgbe: add FFE parameters for user debugging
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-03-29 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 3:17 Jiawen Wu
2021-03-29 3:17 ` [dpdk-dev] [PATCH v4 1/6] net/txgbe: update device ID Jiawen Wu
2021-03-29 3:17 ` [dpdk-dev] [PATCH v4 2/6] net/txgbe: move firmware version get function to base code Jiawen Wu
2021-03-29 3:17 ` [dpdk-dev] [PATCH v4 3/6] net/txgbe: update link setup process of backplane NICs Jiawen Wu
2021-03-29 3:17 ` [dpdk-dev] [PATCH v4 4/6] net/txgbe/base: support to handle backplane AN73 flow Jiawen Wu
2021-03-29 3:17 ` [dpdk-dev] [PATCH v4 5/6] net/txgbe: handle AN interrupt and link update Jiawen Wu
2021-03-29 3:17 ` [dpdk-dev] [PATCH v4 6/6] net/txgbe: add FFE parameters for user debugging Jiawen Wu
2021-03-29 15:50 ` Ferruh Yigit
2021-03-30 1:44 ` Jiawen Wu
2021-03-29 15:51 ` 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=a05f2e08-a69c-a5da-9a4f-b8204e74c9ca@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jiawenwu@trustnetic.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).