From: David Miller <davem@davemloft.net>
To: jarod@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] bonding driver terminology change proposal
Date: Mon, 13 Jul 2020 17:51:37 -0700 (PDT) [thread overview]
Message-ID: <20200713.175137.2050137423148058887.davem@davemloft.net> (raw)
In-Reply-To: <CAKfmpSdcvFG0UTNJFJgXwNRqQb-mk-PsrM5zQ_nXX=RqaaawgQ@mail.gmail.com>
From: Jarod Wilson <jarod@redhat.com>
Date: Mon, 13 Jul 2020 14:51:39 -0400
> To start out with, I'd like to attempt to eliminate as much of the use
> of master and slave in the bonding driver as possible. For the most
> part, I think this can be done without breaking UAPI, but may require
> changes to anything accessing bond info via proc or sysfs.
You can change what you want internally to the driver in order to meet
this objective, but I am positively sure that external facing UAPI has
to be retained.
next prev parent reply other threads:[~2020-07-14 0:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 18:51 [RFC] bonding driver terminology change proposal Jarod Wilson
2020-07-13 21:36 ` Eric Dumazet
2020-07-14 18:01 ` Jarod Wilson
2020-07-13 22:00 ` Michal Kubecek
2020-07-13 22:41 ` Stephen Hemminger
2020-07-14 0:09 ` Michal Kubecek
2020-07-14 0:26 ` Andrew Lunn
2020-07-16 3:04 ` Jarod Wilson
2020-07-16 3:18 ` Andrew Lunn
2020-07-16 5:43 ` Jarod Wilson
2020-08-13 3:42 ` Jarod Wilson
2020-07-14 0:55 ` Jay Vosburgh
2020-07-14 18:15 ` Jarod Wilson
2020-07-15 12:56 ` Edward Cree
2020-07-15 19:23 ` Jarod Wilson
2020-07-14 1:00 ` David Miller
2020-07-16 3:06 ` Jarod Wilson
2020-07-16 18:59 ` David Miller
2020-07-16 23:01 ` Stephen Hemminger
2020-07-14 18:04 ` Jarod Wilson
2020-07-14 0:51 ` David Miller [this message]
2020-07-14 19:17 ` Toke Høiland-Jørgensen
2020-07-14 20:39 ` Marcelo Ricardo Leitner
2020-07-14 21:24 ` Jarod Wilson
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=20200713.175137.2050137423148058887.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jarod@redhat.com \
--cc=netdev@vger.kernel.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).