From: Florian Fainelli <f.fainelli@gmail.com>
To: Vladimir Oltean <olteanv@gmail.com>,
Florian Fainelli <florian.fainelli@broadcom.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
"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>,
"open list:ARM/Mediatek SoC support"
<linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH net-next v4 1/2] net: dsa: Use conduit and user terms
Date: Tue, 17 Oct 2023 20:16:18 -0700 [thread overview]
Message-ID: <127d957f-0af5-4a6b-9c06-003750daaf9c@gmail.com> (raw)
In-Reply-To: <20231017100328.qmwi2dnqay7syoki@skbuf>
On 10/17/2023 3:03 AM, Vladimir Oltean wrote:
> On Mon, Oct 16, 2023 at 09:47:41AM -0700, Florian Fainelli wrote:
>> Use more inclusive terms throughout the DSA subsystem by moving away
>> from "master" which is replaced by "conduit" and "slave" which is
>> replaced by "user". No functional changes.
>>
>> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
>> ---
>
> Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> Note that you left the following unconverted:
Bah, thanks, sent a v5 with those additions. Thank you!
--
Florian
next prev parent reply other threads:[~2023-10-18 3:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 16:47 [PATCH net-next v4 0/2] Switch DSA to inclusive terminology Florian Fainelli
2023-10-16 16:47 ` [PATCH net-next v4 1/2] net: dsa: Use conduit and user terms Florian Fainelli
2023-10-16 18:43 ` Stephen Hemminger
2023-10-17 10:03 ` Vladimir Oltean
2023-10-18 3:16 ` Florian Fainelli [this message]
2023-10-16 16:47 ` [PATCH net-next v4 2/2] net: dsa: Rename IFLA_DSA_MASTER to IFLA_DSA_CONDUIT Florian Fainelli
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=127d957f-0af5-4a6b-9c06-003750daaf9c@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.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
all inboxes | Powered by JetHome®