From: patchwork-bot+netdevbpf@kernel.org
To: Dexuan Cui <decui@microsoft.com>
Cc: davem@davemloft.net, kuba@kernel.org, kys@microsoft.com,
haiyangz@microsoft.com, stephen@networkplumber.org,
sthemmin@microsoft.com, wei.liu@kernel.org, liuwe@microsoft.com,
netdev@vger.kernel.org, leon@kernel.org, andrew@lunn.ch,
bernd@petrovitsch.priv.at, rdunlap@infradead.org,
shacharr@microsoft.com, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org, Joseph.Salisbury@microsoft.com
Subject: Re: [PATCH net-next][REPOST] hv_netvsc: Make netvsc/VF binding check both MAC and serial number
Date: Mon, 26 Apr 2021 01:30:16 +0000 [thread overview]
Message-ID: <161940061604.7794.9498613769256285295.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210424011235.18721-1-decui@microsoft.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 23 Apr 2021 18:12:35 -0700 you wrote:
> Currently the netvsc/VF binding logic only checks the PCI serial number.
>
> The Microsoft Azure Network Adapter (MANA) supports multiple net_device
> interfaces (each such interface is called a "vPort", and has its unique
> MAC address) which are backed by the same VF PCI device, so the binding
> logic should check both the MAC address and the PCI serial number.
>
> [...]
Here is the summary with links:
- [net-next,REPOST] hv_netvsc: Make netvsc/VF binding check both MAC and serial number
https://git.kernel.org/netdev/net-next/c/64ff412ad41f
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-26 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 1:12 [PATCH net-next][REPOST] hv_netvsc: Make netvsc/VF binding check both MAC and serial number Dexuan Cui
2021-04-26 1: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=161940061604.7794.9498613769256285295.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Joseph.Salisbury@microsoft.com \
--cc=andrew@lunn.ch \
--cc=bernd@petrovitsch.priv.at \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwe@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=shacharr@microsoft.com \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.org \
/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).