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 supports
Date: Wed, 21 Sep 2022 12:48:10 +0100 [thread overview]
Message-ID: <cc4836bb-c0f3-0560-ad2b-66842e9afd6b@xilinx.com> (raw)
In-Reply-To: <20220902030011.377523-1-jiawenwu@trustnetic.com>
On 9/2/2022 4:00 AM, Jiawen Wu wrote:
> Fix some bugs, remove unused logic, support new features.
>
> Jiawen Wu (9):
> net/txgbe: fix IPv6 rule in flow director
> net/txgbe: fix OEM customized LED
> net/txgbe: remove semaphore between SW/FW
> net/txgbe: rename some extended statistic
> net/ngbe: rename some extended statistic
> net/ngbe: remove semaphore between SW/FW
> net/ngbe: fix max frame size
> net/ngbe: fix YT PHY mixed mode occasionally failing link
> net/ngbe: support to set link down/up
>
Series applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2022-09-21 11:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 3:00 Jiawen Wu
2022-09-02 3:00 ` [PATCH 1/9] net/txgbe: fix IPv6 rule in flow director Jiawen Wu
2022-09-02 3:00 ` [PATCH 2/9] net/txgbe: fix OEM customized LED Jiawen Wu
2022-09-02 3:00 ` [PATCH 3/9] net/txgbe: remove semaphore between SW/FW Jiawen Wu
2022-09-02 3:00 ` [PATCH 4/9] net/txgbe: rename some extended statistic Jiawen Wu
2022-09-02 3:00 ` [PATCH 5/9] net/ngbe: " Jiawen Wu
2022-09-02 3:00 ` [PATCH 6/9] net/ngbe: remove semaphore between SW/FW Jiawen Wu
2022-09-02 3:00 ` [PATCH 7/9] net/ngbe: fix max frame size Jiawen Wu
2022-09-02 3:00 ` [PATCH 8/9] net/ngbe: fix YT PHY mixed mode occasionally failing link Jiawen Wu
2022-09-02 3:00 ` [PATCH 9/9] net/ngbe: support to set link down/up Jiawen Wu
2022-09-21 11:46 ` Ferruh Yigit
2022-09-13 1:55 ` [PATCH 0/9] Wangxun fixes and supports Jiawen Wu
2022-09-21 11:48 ` Ferruh Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-08 10:11 Jiawen Wu
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=cc4836bb-c0f3-0560-ad2b-66842e9afd6b@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).