All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hao Lan <lanhao@huawei.com>
Cc: netdev@vger.kernel.org, yisen.zhuang@huawei.com,
	salil.mehta@huawei.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, huangguangbin2@huawei.com,
	simon.horman@corigine.com, shaojijie@huawei.com,
	chenhao418@huawei.com, shenjian15@huawei.com,
	liuyonglong@huawei.com, wangjie125@huawei.com,
	yuanjilin@cdjrlc.com, cai.huoqing@linux.dev,
	xiujianfeng@huawei.com, tanhuazhong@huawei.com
Subject: Re: [PATCH net 0/4] net: hns3: There are some bugfixes for the HNS3 ethernet driver
Date: Sat, 13 May 2023 16:30:21 +0000	[thread overview]
Message-ID: <168399542135.7347.589985237371368267.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230512100014.2522-1-lanhao@huawei.com>

Hello:

This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Fri, 12 May 2023 18:00:10 +0800 you wrote:
> There are some bugfixes for the HNS3 ethernet driver.
> Patch#1 fix output information incomplete for dumping tx queue info
>  with debugfs.
> Patch#2 fix sending pfc frames after reset issue.
> Patch#3 fix reset delay time to avoid configuration timeout.
> Patch#4 fix reset timeout when enable full VF.
> 
> [...]

Here is the summary with links:
  - [net,1/4] net: hns3: fix output information incomplete for dumping tx queue info with debugfs
    https://git.kernel.org/netdev/net/c/89f6bfb07118
  - [net,2/4] net: hns3: fix sending pfc frames after reset issue
    https://git.kernel.org/netdev/net/c/f14db0706472
  - [net,3/4] net: hns3: fix reset delay time to avoid configuration timeout
    https://git.kernel.org/netdev/net/c/814d0c786068
  - [net,4/4] net: hns3: fix reset timeout when enable full VF
    https://git.kernel.org/netdev/net/c/6b45d5ff8c2c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-05-13 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 10:00 [PATCH net 0/4] net: hns3: There are some bugfixes for the HNS3 ethernet driver Hao Lan
2023-05-12 10:00 ` [PATCH net 1/4] net: hns3: fix output information incomplete for dumping tx queue info with debugfs Hao Lan
2023-05-12 10:00 ` [PATCH net 2/4] net: hns3: fix sending pfc frames after reset issue Hao Lan
2023-05-12 10:00 ` [PATCH net 3/4] net: hns3: fix reset delay time to avoid configuration timeout Hao Lan
2023-05-12 10:00 ` [PATCH net 4/4] net: hns3: fix reset timeout when enable full VF Hao Lan
2023-05-13 16:30 ` patchwork-bot+netdevbpf [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=168399542135.7347.589985237371368267.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=cai.huoqing@linux.dev \
    --cc=chenhao418@huawei.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=huangguangbin2@huawei.com \
    --cc=kuba@kernel.org \
    --cc=lanhao@huawei.com \
    --cc=liuyonglong@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=salil.mehta@huawei.com \
    --cc=shaojijie@huawei.com \
    --cc=shenjian15@huawei.com \
    --cc=simon.horman@corigine.com \
    --cc=tanhuazhong@huawei.com \
    --cc=wangjie125@huawei.com \
    --cc=xiujianfeng@huawei.com \
    --cc=yisen.zhuang@huawei.com \
    --cc=yuanjilin@cdjrlc.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.