From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/5] net: remove direct netdev->dev_addr writes
Date: Fri, 8 Oct 2021 10:59:08 -0700 [thread overview]
Message-ID: <20211008175913.3754184-1-kuba@kernel.org> (raw)
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 got through appropriate helpers.
This series contains top 5 conversions in terms of LoC required
to bring the driver into compliance.
Jakub Kicinski (5):
ethernet: forcedeth: remove direct netdev->dev_addr writes
ethernet: tg3: remove direct netdev->dev_addr writes
ethernet: tulip: remove direct netdev->dev_addr writes
ethernet: sun: remove direct netdev->dev_addr writes
ethernet: 8390: remove direct netdev->dev_addr writes
drivers/net/ethernet/8390/apne.c | 3 +-
drivers/net/ethernet/8390/ax88796.c | 6 ++-
drivers/net/ethernet/8390/axnet_cs.c | 7 ++-
drivers/net/ethernet/8390/mcf8390.c | 3 +-
drivers/net/ethernet/8390/ne.c | 4 +-
drivers/net/ethernet/8390/pcnet_cs.c | 22 ++++++---
drivers/net/ethernet/8390/stnic.c | 5 +--
drivers/net/ethernet/8390/zorro8390.c | 3 +-
drivers/net/ethernet/broadcom/tg3.c | 48 ++++++++++----------
drivers/net/ethernet/dec/tulip/de2104x.c | 15 ++++---
drivers/net/ethernet/dec/tulip/de4x5.c | 35 +++++++--------
drivers/net/ethernet/dec/tulip/dmfe.c | 9 ++--
drivers/net/ethernet/dec/tulip/tulip_core.c | 37 +++++++++-------
drivers/net/ethernet/dec/tulip/uli526x.c | 11 +++--
drivers/net/ethernet/dec/tulip/xircom_cb.c | 4 +-
drivers/net/ethernet/nvidia/forcedeth.c | 49 +++++++++++----------
drivers/net/ethernet/sun/cassini.c | 7 +--
drivers/net/ethernet/sun/ldmvsw.c | 7 +--
drivers/net/ethernet/sun/niu.c | 42 ++++++++++--------
drivers/net/ethernet/sun/sungem.c | 11 +++--
drivers/net/ethernet/sun/sunhme.c | 15 +++++--
21 files changed, 191 insertions(+), 152 deletions(-)
--
2.31.1
next reply other threads:[~2021-10-08 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 17:59 Jakub Kicinski [this message]
2021-10-08 17:59 ` [PATCH net-next 1/5] ethernet: forcedeth: remove direct netdev->dev_addr writes Jakub Kicinski
2021-10-09 2:22 ` Zhu Yanjun
2021-10-08 17:59 ` [PATCH net-next 2/5] ethernet: tg3: " Jakub Kicinski
2021-10-08 18:57 ` Michael Chan
2021-10-08 17:59 ` [PATCH net-next 3/5] ethernet: tulip: " Jakub Kicinski
2021-10-09 2:35 ` Joe Perches
2021-10-11 13:05 ` Jakub Kicinski
2021-10-08 17:59 ` [PATCH net-next 4/5] ethernet: sun: " Jakub Kicinski
2021-10-08 17:59 ` [PATCH net-next 5/5] ethernet: 8390: " Jakub Kicinski
2021-10-09 11:00 ` [PATCH net-next 0/5] net: " patchwork-bot+netdevbpf
2021-10-09 15:43 ` Joe Perches
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=20211008175913.3754184-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.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).