Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: R4lIrMH1fjl2sLDc77VuumpJBtAgYRZpGcwOASqctkdx62sS4jZFu99zt1b/DdtadFjGTGKjLG
 2uMf+MwXcrfw==
IronPort-SDR: XcHdzAUjgcIQHtmmTnIckvf2Q4YfKoAJFpFpP8BjN2dTqIlFjNike9eDRf227ItDY9yyi8fkBx
 +Cjkgupf1Phw==
From:   "Williams, Dan J" <dan.j.williams@intel.com>
To:     "stephen@networkplumber.org" <stephen@networkplumber.org>,
        "davem@davemloft.net" <davem@davemloft.net>
CC:     "corbet@lwn.net" <corbet@lwn.net>,
        "andrew@lunn.ch" <andrew@lunn.ch>,
        "amitc@mellanox.com" <amitc@mellanox.com>,
        "david@protonic.nl" <david@protonic.nl>,
        "linville@tuxdriver.com" <linville@tuxdriver.com>,
        "marex@denx.de" <marex@denx.de>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux@armlinux.org.uk" <linux@armlinux.org.uk>,
        "petrm@mellanox.com" <petrm@mellanox.com>,
        "hkallweit1@gmail.com" <hkallweit1@gmail.com>,
        "kernel@pengutronix.de" <kernel@pengutronix.de>,
        "christian.herber@nxp.com" <christian.herber@nxp.com>,
        "mkubecek@suse.cz" <mkubecek@suse.cz>,
        "kuba@kernel.org" <kuba@kernel.org>,
        "o.rempel@pengutronix.de" <o.rempel@pengutronix.de>,
        "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
        "mkl@pengutronix.de" <mkl@pengutronix.de>,
        "f.fainelli@gmail.com" <f.fainelli@gmail.com>
Subject: Re: [PATCH ethtool v1] netlink: add master/slave configuration
 support
Thread-Topic: [PATCH ethtool v1] netlink: add master/slave configuration
 support
Thread-Index: AQHWPpR7OD1wKnaFXUKDw1wTopujAQ==
Date:   Tue, 9 Jun 2020 19:30:50 +0000
Message-ID: <4d664ff641dbf3aeab1ecd5eacda220dab9d7d17.camel@intel.com>
References: <20200607153019.3c8d6650@hermes.lan>
         <20200607.164532.964293508393444353.davem@davemloft.net>
         <20200609101935.5716b3bd@hermes.lan>
         <20200609.113633.1866761141966326637.davem@davemloft.net>
In-Reply-To: <20200609.113633.1866761141966326637.davem@davemloft.net>
Accept-Language: en-US
Content-Language: en-US
user-agent: Evolution 3.32.5 (3.32.5-1.fc30) 
Content-Type: text/plain; charset="utf-7"
Content-ID: <0360B25E816BA441BAFD0F63CF3D4BA5@namprd11.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1887d585-c6d2-45fc-864d-08d80cab9e79
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jun 2020 19:30:50.8231
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: UfFnADy84izWNmZ5Z3jDFhjgTvSYk3PWwF5qcAvg/cWJGKuIeWXBmVYPNersvc8siv1fF7/RNImwqp4GbEw1aHBknW3gjSSl93MoZsDpr8s=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1938
X-OriginatorOrg: intel.com
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 2020-06-09 at 11:36 -0700, David Miller wrote:
+AD4- From: Stephen Hemminger +ADw-stephen+AEA-networkplumber.org+AD4-
+AD4- Date: Tue, 9 Jun 2020 10:19:35 -0700
+AD4-=20
+AD4- +AD4- Yes, words do matter and convey a lot of implied connotation an=
d
+AD4- +AD4- meaning.
+AD4-=20
+AD4- What is your long term plan?  Will you change all of the UAPI for
+AD4- bonding for example?

The long term plan in my view includes talking with standards bodies to
move new content to, for example, master/subordinate. In other words,
practical forward steps, not retroactively changing interfaces.

+AD4- Or will we have a partial solution to the problem?

Partial steps toward better inclusion are meaningful.

The root problem is of course much larger than a few changes to
technical terminology could ever solve, but solving +ACo-that+ACo- problem =
is
not the goal. The goal is to make the kernel community as productive as
possible and if the antropomorphic association of +ACI-slave+ACI- can be
replaced with a term that maintains technical meaning it makes kernel-
work that much more approachable.

I recall one of Ingo's explanations of how broken whitespace can make
patches that much harder to read and take him out of the +ACI-zone+ACI- of
reviewing code. +ACI-Slave+ACI- is already having that speed bump affect on=
 the
community. If we can replace it without losing meaning and improving
the effectiveness of contributors I think the Linux kernel project is
better for it.