From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, mst@redhat.com,
jasowang@redhat.com, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH net-next v2] net: virtio: use eth_hw_addr_set()
Date: Thu, 28 Oct 2021 15:20:07 +0000 [thread overview]
Message-ID: <163543440710.20393.2773877623899316813.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211027152012.3393077-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 27 Oct 2021 08:20:12 -0700 you wrote:
> Commit 406f42fa0d3c ("net-next: When a bond have a massive amount
> of VLANs...") introduced a rbtree for faster Ethernet address look
> up. To maintain netdev->dev_addr in this tree we need to make all
> the writes to it go through appropriate helpers.
>
> Even though the current code uses dev->addr_len the we can switch
> to eth_hw_addr_set() instead of dev_addr_set(). The netdev is
> always allocated by alloc_etherdev_mq() and there are at least two
> places which assume Ethernet address:
> - the line below calling eth_hw_addr_random()
> - virtnet_set_mac_address() -> eth_commit_mac_addr_change()
>
> [...]
Here is the summary with links:
- [net-next,v2] net: virtio: use eth_hw_addr_set()
https://git.kernel.org/netdev/net-next/c/f2edaa4ad5d5
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-10-28 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 15:20 [PATCH net-next v2] net: virtio: use eth_hw_addr_set() Jakub Kicinski
2021-10-27 15:30 ` Michael S. Tsirkin
2021-10-27 15:30 ` Michael S. Tsirkin
2021-10-28 2:30 ` Jason Wang
2021-10-28 2:30 ` Jason Wang
2021-10-28 15:20 ` 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=163543440710.20393.2773877623899316813.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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 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.