DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/9] Wangxun bug fixes
Date: Tue, 20 Jun 2023 16:33:16 +0100	[thread overview]
Message-ID: <87ad43a0-34c9-efef-8ffa-a35a3f268a04@amd.com> (raw)
In-Reply-To: <20230614023429.1002071-1-jiawenwu@trustnetic.com>

On 6/14/2023 3:34 AM, Jiawen Wu wrote:
> Fix some bugs for txgbe and ngbe.
> 
> Jiawen Wu (9):
>   net/txgbe: fix Tx failure with fiber hotplug
>   net/txgbe: fix interrupt enable mask
>   net/txgbe: fix issues caused by MNG veto bit setting
>   net/txgbe: fix to set autoneg for 1G speed
>   net/txgbe: fix device extended stats
>   net/ngbe: fix device extended stats
>   net/ngbe: fix issues caused by MNG veto bit setting
>   net/ngbe: fix link status in no LSC mode
>   net/ngbe: remove redundant codes
>

Series applied to dpdk-next-net/main, thanks.


      parent reply	other threads:[~2023-06-20 15:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14  2:34 Jiawen Wu
2023-06-14  2:34 ` [PATCH 1/9] net/txgbe: fix Tx failure with fiber hotplug Jiawen Wu
2023-06-14  2:34 ` [PATCH 2/9] net/txgbe: fix interrupt enable mask Jiawen Wu
2023-06-14  2:34 ` [PATCH 3/9] net/txgbe: fix issues caused by MNG veto bit setting Jiawen Wu
2023-06-14  2:34 ` [PATCH 4/9] net/txgbe: fix to set autoneg for 1G speed Jiawen Wu
2023-06-14  2:34 ` [PATCH 5/9] net/txgbe: fix device extended stats Jiawen Wu
2023-06-14  2:34 ` [PATCH 6/9] net/ngbe: " Jiawen Wu
2023-06-14  2:34 ` [PATCH 7/9] net/ngbe: fix issues caused by MNG veto bit setting Jiawen Wu
2023-06-14  2:34 ` [PATCH 8/9] net/ngbe: fix link status in no LSC mode Jiawen Wu
2023-06-14  2:34 ` [PATCH 9/9] net/ngbe: remove redundant codes Jiawen Wu
2023-06-19  2:23 ` [PATCH 0/9] Wangxun bug fixes Jiawen Wu
2023-06-20 15:33 ` 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=87ad43a0-34c9-efef-8ffa-a35a3f268a04@amd.com \
    --to=ferruh.yigit@amd.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).