[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202006091222.CB97F743AD@keescook>
Date: Tue, 9 Jun 2020 12:29:54 -0700
From: Kees Cook <keescook@...omium.org>
To: David Miller <davem@...emloft.net>
Cc: stephen@...workplumber.org, o.rempel@...gutronix.de,
andrew@...n.ch, f.fainelli@...il.com, hkallweit1@...il.com,
kuba@...nel.org, corbet@....net, mkubecek@...e.cz,
linville@...driver.com, david@...tonic.nl, kernel@...gutronix.de,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux@...linux.org.uk, mkl@...gutronix.de, marex@...x.de,
christian.herber@....com, amitc@...lanox.com, petrm@...lanox.com
Subject: Re: [PATCH ethtool v1] netlink: add master/slave configuration
support
On Tue, Jun 09, 2020 at 11:36:33AM -0700, David Miller wrote:
> From: Stephen Hemminger <stephen@...workplumber.org>
> Date: Tue, 9 Jun 2020 10:19:35 -0700
>
> > Yes, words do matter and convey a lot of implied connotation and
> > meaning.
>
> What is your long term plan? Will you change all of the UAPI for
> bonding for example?
>
> Or will we have a partial solution to the problem?
As a first step, let's stop _adding_ this language.
Given what I've seen from other communities and what I know of the kernel
community, I don't think we're going to get consensus on some massive
global search/replace any time soon. However, I think we can get started
on making this change with just stopping further introductions. (I view
this like any other treewide change: stop new badness from getting
added, and chip away as old ones as we can until it's all gone.)
--
Kees Cook
Powered by blists - more mailing lists