From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
stefanr@s5r6.in-berlin.de, linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH net-next] firewire: don't write directly to netdev->dev_addr
Date: Thu, 28 Oct 2021 12:20:12 +0000 [thread overview]
Message-ID: <163542361293.29870.11627651089310306022.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211026175352.3197750-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 26 Oct 2021 10:53:52 -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.
>
> Prepare fwnet_hwaddr on the stack and use dev_addr_set() to copy
> it to netdev->dev_addr. We no longer need to worry about alignment.
> union fwnet_hwaddr does not have any padding and we set all fields
> so we don't need to zero it upfront.
>
> [...]
Here is the summary with links:
- [net-next] firewire: don't write directly to netdev->dev_addr
https://git.kernel.org/netdev/net-next/c/aaaaa1377e7a
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 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 17:53 [PATCH net-next] firewire: don't write directly to netdev->dev_addr Jakub Kicinski
2021-10-28 12: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=163542361293.29870.11627651089310306022.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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.