From: David Miller <davem@davemloft.net>
To: dan.j.williams@intel.com
Cc: stephen@networkplumber.org, corbet@lwn.net, andrew@lunn.ch,
amitc@mellanox.com, david@protonic.nl, linville@tuxdriver.com,
marex@denx.de, linux-kernel@vger.kernel.org,
linux@armlinux.org.uk, petrm@mellanox.com, hkallweit1@gmail.com,
kernel@pengutronix.de, christian.herber@nxp.com,
mkubecek@suse.cz, kuba@kernel.org, o.rempel@pengutronix.de,
netdev@vger.kernel.org, mkl@pengutronix.de, f.fainelli@gmail.com
Subject: Re: [PATCH ethtool v1] netlink: add master/slave configuration support
Date: Tue, 09 Jun 2020 12:38:58 -0700 (PDT) [thread overview]
Message-ID: <20200609.123858.466960203090925019.davem@davemloft.net> (raw)
In-Reply-To: <4d664ff641dbf3aeab1ecd5eacda220dab9d7d17.camel@intel.com>
From: "Williams, Dan J" <dan.j.williams@intel.com>
Date: Tue, 9 Jun 2020 19:30:50 +0000
> On Tue, 2020-06-09 at 11:36 -0700, David Miller wrote:
>> From: Stephen Hemminger <stephen@networkplumber.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?
>
> 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.
When that knowledge is established legitimately in standards and
transferred into common knowledge of these technologies, yes then
please come present your proposals.
But right now using different words will create confusion.
I also find master/subordinate an interesting proposal, what if master
is a triggering term? Why only slave?
I know people feel something needs to change, but do that moving
forward for the technologies themselves. Not how we implement support
for a technology which is established already.
Plant the seed, don't chop the tree down.
next prev parent reply other threads:[~2020-06-09 19:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 9:10 [PATCH ethtool v1] netlink: add master/slave configuration support Oleksij Rempel
2020-05-26 12:41 ` Michal Kubecek
2020-05-27 10:26 ` Oleksij Rempel
2020-06-07 22:30 ` Stephen Hemminger
2020-06-07 23:45 ` David Miller
2020-06-09 17:19 ` Stephen Hemminger
2020-06-09 18:30 ` Andrew Lunn
2020-06-09 18:36 ` David Miller
2020-06-09 19:29 ` Kees Cook
2020-06-09 19:34 ` David Miller
2020-06-09 19:49 ` Kees Cook
2020-06-09 20:05 ` David Miller
2020-06-09 20:29 ` Kees Cook
2020-06-09 20:53 ` Michal Kubecek
2020-06-09 21:34 ` Kees Cook
2020-06-09 19:30 ` Williams, Dan J
2020-06-09 19:38 ` David Miller [this message]
2020-06-09 21:48 ` Dan Williams
2020-06-10 6:07 ` Oleksij Rempel
2020-06-09 18:46 ` Edward Cree
2020-06-09 20:31 ` Michal Kubecek
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=20200609.123858.466960203090925019.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amitc@mellanox.com \
--cc=andrew@lunn.ch \
--cc=christian.herber@nxp.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=david@protonic.nl \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linville@tuxdriver.com \
--cc=marex@denx.de \
--cc=mkl@pengutronix.de \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=petrm@mellanox.com \
--cc=stephen@networkplumber.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).