From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'Ferruh Yigit'" <ferruh.yigit@xilinx.com>, <dev@dpdk.org>
Subject: RE: [PATCH v2 0/7] Fixes and supports for Wangxun NICs
Date: Thu, 23 Jun 2022 11:26:17 +0800 [thread overview]
Message-ID: <011e01d886b1$008577f0$019067d0$@trustnetic.com> (raw)
In-Reply-To: <36eb6b4f-8b45-782a-f576-dcad80c09499@xilinx.com>
On Wednesday, June 22, 2022 6:56 PM, Ferruh Yigit wrote:
> On 6/22/2022 7:56 AM, Jiawen Wu wrote:
> > Fix the remaining bugs, support more OEM devices.
> >
> > v2:
> > - remove useless variable initializers
> > - define macros for loop counts
> > - supplement detailed commit log
> >
> > Jiawen Wu (7):
> > net/txgbe: support OEM subsystem vendor ID
> > net/ngbe: support OEM subsystem vendor ID
> > net/txgbe: fix register polling
> > net/ngbe: add more packet statistics
> > net/ngbe: fix YT PHY UTP mode to link up
> > net/ngbe: support autoneg on/off for external PHY SFI mode
> > net/ngbe: support YT PHY SGMII to RGMII mode
> >
>
> Series applied to dpdk-next-net/main, thanks.
>
>
> Please send new version of the sets as reply to previous version to keep them
> all in same email thread.
Okay, get it.
prev parent reply other threads:[~2022-06-23 3:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 6:56 Jiawen Wu
2022-06-22 6:56 ` [PATCH v2 1/7] net/txgbe: support OEM subsystem vendor ID Jiawen Wu
2022-06-22 6:56 ` [PATCH v2 2/7] net/ngbe: " Jiawen Wu
2022-06-22 6:56 ` [PATCH v2 3/7] net/txgbe: fix register polling Jiawen Wu
2022-06-22 6:56 ` [PATCH v2 4/7] net/ngbe: add more packet statistics Jiawen Wu
2022-06-22 6:56 ` [PATCH v2 5/7] net/ngbe: fix YT PHY UTP mode to link up Jiawen Wu
2022-06-22 6:56 ` [PATCH v2 6/7] net/ngbe: support autoneg on/off for external PHY SFI mode Jiawen Wu
2022-06-22 6:56 ` [PATCH v2 7/7] net/ngbe: support YT PHY SGMII to RGMII mode Jiawen Wu
2022-06-22 10:56 ` [PATCH v2 0/7] Fixes and supports for Wangxun NICs Ferruh Yigit
2022-06-23 3:26 ` Jiawen Wu [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='011e01d886b1$008577f0$019067d0$@trustnetic.com' \
--to=jiawenwu@trustnetic.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.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).