From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
j.vosburgh@gmail.com, t.sailer@alumni.ethz.ch, jreuter@yaina.de,
jpr@f6fbb.org, sridhar.samudrala@intel.com, jiri@resnulli.us,
jes@trained-monkey.org
Subject: Re: [PATCH net-next] net: use dev_addr_set()
Date: Sat, 09 Oct 2021 11:00:08 +0000 [thread overview]
Message-ID: <163377720846.21740.10133198972390012435.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211008175339.3753696-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 8 Oct 2021 10:53:39 -0700 you wrote:
> Use dev_addr_set() instead of writing directly to netdev->dev_addr
> in various misc and old drivers.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> drivers/net/bonding/bond_main.c | 2 +-
> drivers/net/hamradio/baycom_epp.c | 2 +-
> drivers/net/hamradio/bpqether.c | 2 +-
> drivers/net/hamradio/dmascc.c | 3 +--
> drivers/net/hamradio/hdlcdrv.c | 2 +-
> drivers/net/hamradio/scc.c | 2 +-
> drivers/net/hamradio/yam.c | 2 +-
> drivers/net/net_failover.c | 3 +--
> drivers/net/ntb_netdev.c | 2 +-
> drivers/net/team/team.c | 2 +-
> drivers/net/vmxnet3/vmxnet3_drv.c | 4 ++--
> drivers/net/wan/lapbether.c | 2 +-
> net/802/hippi.c | 2 +-
> net/atm/br2684.c | 2 +-
> net/netrom/nr_dev.c | 2 +-
> net/rose/rose_dev.c | 2 +-
> 16 files changed, 17 insertions(+), 19 deletions(-)
Here is the summary with links:
- [net-next] net: use dev_addr_set()
https://git.kernel.org/netdev/net-next/c/ea52a0b58e41
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-09 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 17:53 [PATCH net-next] net: use dev_addr_set() Jakub Kicinski
2021-10-09 11: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=163377720846.21740.10133198972390012435.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=j.vosburgh@gmail.com \
--cc=jes@trained-monkey.org \
--cc=jiri@resnulli.us \
--cc=jpr@f6fbb.org \
--cc=jreuter@yaina.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
--cc=t.sailer@alumni.ethz.ch \
/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).