From: patchwork-bot+netdevbpf@kernel.org
To: Huazhong Tan <tanhuazhong@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
salil.mehta@huawei.com, yisen.zhuang@huawei.com,
huangdaode@huawei.com, linuxarm@openeuler.org,
linuxarm@huawei.com
Subject: Re: [PATCH RESEND net-next 0/2] net: hns3: updates for -next
Date: Fri, 16 Apr 2021 00:00:10 +0000 [thread overview]
Message-ID: <161853121003.2137.949633143176457701.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1618453239-10451-1-git-send-email-tanhuazhong@huawei.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 15 Apr 2021 10:20:37 +0800 you wrote:
> This series adds support for pushing link status to VFs for
> the HNS3 ethernet driver.
>
> Guangbin Huang (2):
> net: hns3: PF add support for pushing link status to VFs
> net: hns3: VF not request link status when PF support push link status
> feature
>
> [...]
Here is the summary with links:
- [RESEND,net-next,1/2] net: hns3: PF add support for pushing link status to VFs
https://git.kernel.org/netdev/net-next/c/18b6e31f8bf4
- [RESEND,net-next,2/2] net: hns3: VF not request link status when PF support push link status feature
https://git.kernel.org/netdev/net-next/c/01305e16ebe7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-04-16 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 2:20 [PATCH RESEND net-next 0/2] net: hns3: updates for -next Huazhong Tan
2021-04-15 2:20 ` [PATCH RESEND net-next 1/2] net: hns3: PF add support for pushing link status to VFs Huazhong Tan
2021-04-15 2:20 ` [PATCH RESEND net-next 2/2] net: hns3: VF not request link status when PF support push link status feature Huazhong Tan
2021-04-16 0:00 ` 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=161853121003.2137.949633143176457701.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=huangdaode@huawei.com \
--cc=kuba@kernel.org \
--cc=linuxarm@huawei.com \
--cc=linuxarm@openeuler.org \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=tanhuazhong@huawei.com \
--cc=yisen.zhuang@huawei.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.