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@huawei.com
Subject: Re: [PATCH net-next 0/2] net: hns3: add two promisc mode updates
Date: Mon, 24 May 2021 20:30:10 +0000 [thread overview]
Message-ID: <162188821067.23443.13861638200984980870.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1621848643-18567-1-git-send-email-tanhuazhong@huawei.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 24 May 2021 17:30:41 +0800 you wrote:
> This series includes two updates related to promisc mode for the HNS3
> ethernet driver.
>
> Jian Shen (2):
> net: hns3: configure promisc mode for VF asynchronously
> net: hns3: use HCLGE_VPORT_STATE_PROMISC_CHANGE to replace
> HCLGE_STATE_PROMISC_CHANGED
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: hns3: configure promisc mode for VF asynchronously
https://git.kernel.org/netdev/net-next/c/1e6e76101fd9
- [net-next,2/2] net: hns3: use HCLGE_VPORT_STATE_PROMISC_CHANGE to replace HCLGE_STATE_PROMISC_CHANGED
https://git.kernel.org/netdev/net-next/c/4e2471f7b6ef
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-05-24 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 9:30 [PATCH net-next 0/2] net: hns3: add two promisc mode updates Huazhong Tan
2021-05-24 9:30 ` [PATCH net-next 1/2] net: hns3: configure promisc mode for VF asynchronously Huazhong Tan
2021-05-24 9:30 ` [PATCH net-next 2/2] net: hns3: use HCLGE_VPORT_STATE_PROMISC_CHANGE to replace HCLGE_STATE_PROMISC_CHANGED Huazhong Tan
2021-05-24 20: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=162188821067.23443.13861638200984980870.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=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 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).