From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'Ferruh Yigit'" <ferruh.yigit@intel.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 6/6] net/txgbe: add FFE parameters for user debugging
Date: Tue, 30 Mar 2021 09:44:32 +0800 [thread overview]
Message-ID: <013d01d72506$3bf23700$b3d6a500$@trustnetic.com> (raw)
In-Reply-To: <340415cc-5bd4-f0b8-1116-2bfc16bf49b3@intel.com>
On March 29, 2021 11:51 PM, Ferruh Yigit wrote:
> On 3/29/2021 4:17 AM, Jiawen Wu wrote:
> > Support to set PHY link mode by user defined.
> > And update release notes 21.05 for txgbe.
> >
>
> During merge, release notes update moved to 3/6 where looks more
> appropriate, since this patch adds FFE parameters but note is about AN
> training. But please let me know if it is wrong.
>
That's right, thanks.
> > Signed-off-by: Jiawen Wu <jiawenwu@trustnetic.com>
>
> <...>
>
next prev parent reply other threads:[~2021-03-30 1:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 3:17 [dpdk-dev] [PATCH v4 0/6] txgbe backplane AN training 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 [this message]
2021-03-29 15:51 ` [dpdk-dev] [PATCH v4 0/6] txgbe backplane AN training Ferruh Yigit
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='013d01d72506$3bf23700$b3d6a500$@trustnetic.com' \
--to=jiawenwu@trustnetic.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.