From: Florian Fainelli <florian.fainelli@broadcom.com>
To: netdev@vger.kernel.org
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
linux-kernel@vger.kernel.org (open list:ARM/Mediatek SoC support),
linux-arm-kernel@lists.infradead.org (moderated
list:ARM/Mediatek SoC support)
Subject: [PATCH net-next v3 0/2] Switch DSA to inclusive terminology
Date: Fri, 13 Oct 2023 14:52:49 -0700 [thread overview]
Message-ID: <20231013215251.152912-1-florian.fainelli@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5216 bytes --]
One of the action items following Netconf'23 is to switch subsystems to
use inclusive terminology. DSA has been making extensive use of the
"master" and "slave" words which are now replaced by "conduit" and
"user" respectively.
Changes in v3:
- properly align arguments with the changed function names
- ensure markup delimiters lengths are corrected to the name word length
- maintain the existing wording about LAG devices
Changes in v2:
- addressed kbuild test robots reports
- preserve capitalization where relevant
- fixed build error in mtk_ppe_offload.c
Florian Fainelli (2):
net: dsa: Use conduit and user terms
net: dsa: Rename IFLA_DSA_MASTER to IFLA_DSA_CONDUIT
.../bindings/net/dsa/mediatek,mt7530.yaml | 2 +-
Documentation/networking/dsa/b53.rst | 14 +-
Documentation/networking/dsa/bcm_sf2.rst | 2 +-
.../networking/dsa/configuration.rst | 102 +-
Documentation/networking/dsa/dsa.rst | 156 +-
Documentation/networking/dsa/lan9303.rst | 2 +-
Documentation/networking/dsa/sja1105.rst | 6 +-
.../dts/marvell/armada-3720-espressobin.dtsi | 2 +-
drivers/net/dsa/b53/b53_common.c | 4 +-
drivers/net/dsa/b53/b53_mdio.c | 2 +-
drivers/net/dsa/bcm_sf2.c | 36 +-
drivers/net/dsa/bcm_sf2.h | 2 +-
drivers/net/dsa/bcm_sf2_cfp.c | 4 +-
drivers/net/dsa/lan9303-core.c | 4 +-
drivers/net/dsa/lantiq_gswip.c | 34 +-
drivers/net/dsa/microchip/ksz9477.c | 6 +-
drivers/net/dsa/microchip/ksz_common.c | 20 +-
drivers/net/dsa/microchip/ksz_ptp.c | 2 +-
drivers/net/dsa/mt7530.c | 16 +-
drivers/net/dsa/mv88e6xxx/chip.c | 2 +-
drivers/net/dsa/ocelot/felix.c | 68 +-
drivers/net/dsa/ocelot/felix.h | 6 +-
drivers/net/dsa/qca/qca8k-8xxx.c | 50 +-
drivers/net/dsa/qca/qca8k-common.c | 2 +-
drivers/net/dsa/qca/qca8k-leds.c | 6 +-
drivers/net/dsa/qca/qca8k.h | 2 +-
drivers/net/dsa/realtek/realtek-smi.c | 28 +-
drivers/net/dsa/realtek/realtek.h | 2 +-
drivers/net/dsa/sja1105/sja1105_main.c | 4 +-
drivers/net/dsa/xrs700x/xrs700x.c | 12 +-
drivers/net/ethernet/broadcom/bcmsysport.c | 2 +-
drivers/net/ethernet/mediatek/mtk_eth_soc.c | 2 +-
.../net/ethernet/mediatek/mtk_ppe_offload.c | 2 +-
include/linux/dsa/sja1105.h | 2 +-
include/net/dsa.h | 56 +-
include/net/dsa_stubs.h | 22 +-
include/uapi/linux/if_link.h | 4 +-
net/core/dev_ioctl.c | 2 +-
net/dsa/Makefile | 6 +-
net/dsa/{master.c => conduit.c} | 118 +-
net/dsa/conduit.h | 22 +
net/dsa/dsa.c | 222 +--
net/dsa/dsa.h | 12 +-
net/dsa/master.h | 22 -
net/dsa/netlink.c | 22 +-
net/dsa/port.c | 124 +-
net/dsa/port.h | 4 +-
net/dsa/slave.h | 69 -
net/dsa/switch.c | 18 +-
net/dsa/switch.h | 4 +-
net/dsa/tag.c | 10 +-
net/dsa/tag.h | 26 +-
net/dsa/tag_8021q.c | 22 +-
net/dsa/tag_8021q.h | 2 +-
net/dsa/tag_ar9331.c | 4 +-
net/dsa/tag_brcm.c | 14 +-
net/dsa/tag_dsa.c | 6 +-
net/dsa/tag_gswip.c | 4 +-
net/dsa/tag_hellcreek.c | 4 +-
net/dsa/tag_ksz.c | 12 +-
net/dsa/tag_lan9303.c | 4 +-
net/dsa/tag_mtk.c | 4 +-
net/dsa/tag_none.c | 6 +-
net/dsa/tag_ocelot.c | 22 +-
net/dsa/tag_ocelot_8021q.c | 12 +-
net/dsa/tag_qca.c | 6 +-
net/dsa/tag_rtl4_a.c | 6 +-
net/dsa/tag_rtl8_4.c | 6 +-
net/dsa/tag_rzn1_a5psw.c | 4 +-
net/dsa/tag_sja1105.c | 30 +-
net/dsa/tag_trailer.c | 4 +-
net/dsa/tag_xrs700x.c | 4 +-
net/dsa/{slave.c => user.c} | 1462 ++++++++---------
net/dsa/user.h | 69 +
74 files changed, 1539 insertions(+), 1537 deletions(-)
rename net/dsa/{master.c => conduit.c} (76%)
create mode 100644 net/dsa/conduit.h
delete mode 100644 net/dsa/master.h
delete mode 100644 net/dsa/slave.h
rename net/dsa/{slave.c => user.c} (62%)
create mode 100644 net/dsa/user.h
--
2.34.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
next reply other threads:[~2023-10-13 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 21:52 Florian Fainelli [this message]
2023-10-13 21:52 ` [PATCH net-next v3 1/2] net: dsa: Use conduit and user terms Florian Fainelli
2023-10-16 13:23 ` Vladimir Oltean
2023-10-16 16:41 ` Florian Fainelli
2023-10-16 19:05 ` Vladimir Oltean
2023-10-13 21:52 ` [PATCH net-next v3 2/2] net: dsa: Rename IFLA_DSA_MASTER to IFLA_DSA_CONDUIT Florian Fainelli
2023-10-14 0:26 ` [PATCH net-next v3 0/2] Switch DSA to inclusive terminology Stephen Hemminger
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=20231013215251.152912-1-florian.fainelli@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
/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).