From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH 0/9] Wangxun fixes and new supports
Date: Tue, 31 May 2022 08:45:49 +0100 [thread overview]
Message-ID: <1df6968d-a5e1-103f-6d2c-cf38d084211e@xilinx.com> (raw)
In-Reply-To: <20220530093016.16326-1-jiawenwu@trustnetic.com>
On 5/30/2022 10:30 AM, Jiawen Wu wrote:
> [CAUTION: External Email]
>
> Fixed some bugs for ngbe and txgbe, and support a new PHY ID.
>
> Jiawen Wu (9):
> net/ngbe: fix to set force speed
> net/ngbe: add support for yt8531s PHY
> net/ngbe: fix occasional failure of reading PHY ID
> net/ngbe: fix external PHY to power down
> net/ngbe: fix to read M88E1512 PHY mode
> net/ngbe: change PCIe related operations to use rte API
> net/ngbe: redesign internal PHY init flow
> net/txgbe: fix SGMII mode to link up
> net/txgbe: fix max number of queues for SRIOV
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-05-31 7:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 9:30 Jiawen Wu
2022-05-30 9:30 ` [PATCH 1/9] net/ngbe: fix to set force speed Jiawen Wu
2022-05-30 9:30 ` [PATCH 2/9] net/ngbe: add support for yt8531s PHY Jiawen Wu
2022-05-30 9:30 ` [PATCH 3/9] net/ngbe: fix occasional failure of reading PHY ID Jiawen Wu
2022-05-30 9:30 ` [PATCH 4/9] net/ngbe: fix external PHY to power down Jiawen Wu
2022-05-30 9:30 ` [PATCH 5/9] net/ngbe: fix to read M88E1512 PHY mode Jiawen Wu
2022-05-30 9:30 ` [PATCH 6/9] net/ngbe: change PCIe related operations to use rte API Jiawen Wu
2022-05-30 9:30 ` [PATCH 7/9] net/ngbe: redesign internal PHY init flow Jiawen Wu
2022-05-30 9:30 ` [PATCH 8/9] net/txgbe: fix SGMII mode to link up Jiawen Wu
2022-05-30 9:30 ` [PATCH 9/9] net/txgbe: fix max number of queues for SRIOV Jiawen Wu
2022-05-31 7:45 ` 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=1df6968d-a5e1-103f-6d2c-cf38d084211e@xilinx.com \
--to=ferruh.yigit@xilinx.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).