Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1594062pxk; Fri, 2 Oct 2020 13:45:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyN/9dnNFTz/+gNZm9Ye22KEjugdFRPA39FfQJPRxa+Bptjzaom4Y7lNS9HNpu1LdHr4N2t X-Received: by 2002:a17:906:a2cf:: with SMTP id by15mr3857441ejb.298.1601671528634; Fri, 02 Oct 2020 13:45:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601671528; cv=none; d=google.com; s=arc-20160816; b=qsx0opizJAQuI8Nyt9LpoLLQXLk06lunF+UWlAYguBlsunkBkfzXgYy03oCuUavvFU AHNWpJCQnFrSjrVv5DfdHmct6/MVlQcmKamTkUe58ErDKdg9Dewt1OFi9tHyr47OX0io Wfl9ga8dVDqb0ltF5EfG1NgvGTJMXjM32xHCkyG/8N+yPM7C7r+EYAreXN390yHZnOX5 7YEKpo94gGTxC/IY7SPxjtdWXq5Tdg9k6k7uTB0A10usWPQmG3WRHFyfLfTOM8eoQNZk HelPymhyyA7BMP8DOQvkUsjPMQfLqauqxQl5bKs+cU2NTyhZXxOeJOsGDSpdV+VTj40J eVrA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=1lrde7GbhA75U6v+6AzDS5QmDQ9wsNKMUkOxg2kLm98=; b=Biq1WOIaI3t8JD7CAi8Iuic/KntwN2SlvfK3Yu9fJvkto8+fN60im3FqoMQ4lYHLtj 7p+/9HMAU3/7Kl3c2WGWaA53TJe1nbMbYfM9OYvpJKNYoflYG9uiS5WfIptQ04xWptQw 0d4OYJPYSwY/jR2uF+zC2OM0YPqAM0/g7qtAHFTBxyVcyT+IqJlFaYyKEcRR2ujo0bIU CddxVbR10ZFrrl6JmEIa2pgjcC5B3F+ieoVP+6zphHEHRNZySKTJrYk5d+x2C4GHfxRD mFl5sgY5QUpU8cuphwrvgranhvWpDIC3MS+1CtkCEar+IkSb0mIHSFuREyUw5m2wVpLW ntwA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o18si1794359ejg.313.2020.10.02.13.45.05; Fri, 02 Oct 2020 13:45:28 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725782AbgJBUnb (ORCPT + 99 others); Fri, 2 Oct 2020 16:43:31 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:41172 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725283AbgJBUnb (ORCPT ); Fri, 2 Oct 2020 16:43:31 -0400 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1kORtl-00HK49-7P; Fri, 02 Oct 2020 22:43:25 +0200 Date: Fri, 2 Oct 2020 22:43:25 +0200 From: Andrew Lunn To: Jarod Wilson Cc: LKML , Jay Vosburgh , Veaceslav Falico , Andy Gospodarek , "David S. Miller" , Jakub Kicinski , Thomas Davis , Netdev Subject: Re: [PATCH net-next v2 5/6] bonding: update Documentation for port/bond terminology Message-ID: <20201002204325.GJ3996795@lunn.ch> References: <20201002174001.3012643-1-jarod@redhat.com> <20201002174001.3012643-6-jarod@redhat.com> <20201002180906.GG3996795@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 02, 2020 at 04:17:34PM -0400, Jarod Wilson wrote: > On Fri, Oct 2, 2020 at 2:09 PM Andrew Lunn 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 > > > Cc: Veaceslav Falico > > > Cc: Andy Gospodarek > > > Cc: "David S. Miller" > > > Cc: Jakub Kicinski > > > Cc: Thomas Davis > > > Cc: netdev@vger.kernel.org > > > Signed-off-by: Jarod Wilson > > > --- > > > 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? I'm assuming you want to deprecate the old language? So i was expecting the language to change. I would expect some explanation of why the names have changed, and a table listing the old and new name. We cannot completely get away from the old names, because they are ABI, so we need to keep documenting them somehow. Andrew