lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 2 Oct 2020 16:17:34 -0400 From: Jarod Wilson <jarod@...hat.com> To: Andrew Lunn <andrew@...n.ch> Cc: LKML <linux-kernel@...r.kernel.org>, Jay Vosburgh <j.vosburgh@...il.com>, Veaceslav Falico <vfalico@...il.com>, Andy Gospodarek <andy@...yhouse.net>, "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Thomas Davis <tadavis@....gov>, Netdev <netdev@...r.kernel.org> Subject: Re: [PATCH net-next v2 5/6] bonding: update Documentation for port/bond terminology On Fri, Oct 2, 2020 at 2:09 PM Andrew Lunn <andrew@...n.ch> wrote: > > On Fri, Oct 02, 2020 at 01:40:00PM -0400, Jarod Wilson wrote: > > Point users to the new interface names instead of the old ones, where > > appropriate. Userspace bits referenced still include use of master/slave, > > but those can't be altered until userspace changes too, ideally after > > these changes propagate to the community at large. > > > > Cc: Jay Vosburgh <j.vosburgh@...il.com> > > Cc: Veaceslav Falico <vfalico@...il.com> > > Cc: Andy Gospodarek <andy@...yhouse.net> > > Cc: "David S. Miller" <davem@...emloft.net> > > Cc: Jakub Kicinski <kuba@...nel.org> > > Cc: Thomas Davis <tadavis@....gov> > > Cc: netdev@...r.kernel.org > > Signed-off-by: Jarod Wilson <jarod@...hat.com> > > --- > > Documentation/networking/bonding.rst | 440 +++++++++++++-------------- > > 1 file changed, 220 insertions(+), 220 deletions(-) > > > > diff --git a/Documentation/networking/bonding.rst b/Documentation/networking/bonding.rst > > index adc314639085..f4c4f0fae83b 100644 > > --- a/Documentation/networking/bonding.rst > > +++ b/Documentation/networking/bonding.rst > > @@ -167,22 +167,22 @@ or, for backwards compatibility, the option value. E.g., > > > > The parameters are as follows: > > > > -active_slave > > +active_port > > Hi Jarod > > It is going to take quite a while before all distributions user space > gets updated. So todays API is going to live on for a few > years. People are going to be search the documentation using the terms > their user space uses, which are going to be todays terms, not the new > ones you are introducing here. For that to work, i think you are going > to have to introduce a table listing todays names and the new names > you are adding, so search engines have some chance of finding this > document, and readers have some clue as to how to translate from what > their user space is using to the terms used in the document. Hm. Would a simple blurb describing the when the changes were made and why at the top of bonding.rst be sufficient? And then would the rest of the doc remain as-is (old master/slave language), or with terminology conversions? -- Jarod Wilson jarod@...hat.com
Powered by blists - more mailing lists