From: Vinod Koul <vkoul@kernel.org> To: Dan Williams <dan.j.williams@intel.com> Cc: ksummit-discuss@lists.linuxfoundation.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, SeongJae Park <sjpark@amazon.de>, linux-kernel@vger.kernel.org, tech-board-discuss@lists.linuxfoundation.org, James Bottomley <James.Bottomley@hansenpartnership.com>, Dave Airlie <airlied@redhat.com>, Christian Brauner <christian.brauner@ubuntu.com>, Dan Carpenter <dan.carpenter@oracle.com> Subject: Re: [Ksummit-discuss] [PATCH v3] CodingStyle: Inclusive Terminology Date: Mon, 13 Jul 2020 09:50:43 +0530 [thread overview] Message-ID: <20200713042043.GN34333@vkoul-mobl> (raw) In-Reply-To: <159423201991.2466245.8461410729774664077.stgit@dwillia2-desk3.amr.corp.intel.com> Hi Dan, On 08-07-20, 11:14, Dan Williams wrote: > Linux maintains a coding-style and its own idiomatic set of terminology. > Update the style guidelines to recommend replacements for the terms > master/slave and blacklist/whitelist. > > Link: http://lore.kernel.org/r/159389297140.2210796.13590142254668787525.stgit@dwillia2-desk3.amr.corp.intel.com > Acked-by: Randy Dunlap <rdunlap@infradead.org> > Acked-by: Dave Airlie <airlied@redhat.com> > Acked-by: SeongJae Park <sjpark@amazon.de> > Acked-by: Christian Brauner <christian.brauner@ubuntu.com> > Acked-by: James Bottomley <James.Bottomley@HansenPartnership.com> > Reviewed-by: Mark Brown <broonie@kernel.org> > Signed-off-by: Theodore Ts'o <tytso@mit.edu> > Signed-off-by: Shuah Khan <skhan@linuxfoundation.org> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> > Signed-off-by: Kees Cook <keescook@chromium.org> > Signed-off-by: Olof Johansson <olof@lixom.net> > Signed-off-by: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Chris Mason <clm@fb.com> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> > Signed-off-by: Dan Williams <dan.j.williams@intel.com> Acked-By: Vinod Koul <vkoul@kernel.org> Thanks for working on this > --- > Changes since v2 [1]: > - Pick up missed sign-offs and acks from Jon, Shuah, and Christian > (sorry about missing those earlier). > > - Reformat the replacement list to make it easier to read. > > - Add 'controller' as a suggested replacement (Kees and Mark) > > - Fix up the paired term for 'performer' to be 'director' (Kees) > > - Collect some new acks, reviewed-by's, and sign-offs for v2. > > - Fix up Chris's email > > [1]: http://lore.kernel.org/r/159419296487.2464622.863943877093636532.stgit@dwillia2-desk3.amr.corp.intel.com > > > Documentation/process/coding-style.rst | 20 ++++++++++++++++++++ > 1 file changed, 20 insertions(+) > > diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst > index 2657a55c6f12..1bee6f8affdb 100644 > --- a/Documentation/process/coding-style.rst > +++ b/Documentation/process/coding-style.rst > @@ -319,6 +319,26 @@ If you are afraid to mix up your local variable names, you have another > problem, which is called the function-growth-hormone-imbalance syndrome. > See chapter 6 (Functions). > > +For symbol names and documentation, avoid introducing new usage of > +'master / slave' (or 'slave' independent of 'master') and 'blacklist / > +whitelist'. > + > +Recommended replacements for 'master / slave' are: > + '{primary,main} / {secondary,replica,subordinate}' > + '{initiator,requester} / {target,responder}' > + '{controller,host} / {device,worker,proxy}' > + 'leader / follower' > + 'director / performer' > + > +Recommended replacements for 'blacklist/whitelist' are: > + 'denylist / allowlist' > + 'blocklist / passlist' > + > +Exceptions for introducing new usage is to maintain a userspace ABI/API, > +or when updating code for an existing (as of 2020) hardware or protocol > +specification that mandates those terms. For new specifications > +translate specification usage of the terminology to the kernel coding > +standard where possible. > > 5) Typedefs > ----------- > > _______________________________________________ > Ksummit-discuss mailing list > Ksummit-discuss@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss -- ~Vinod _______________________________________________ Ksummit-discuss mailing list Ksummit-discuss@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2020-07-13 4:20 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-08 18:14 Dan Williams 2020-07-09 7:25 ` Daniel Vetter 2020-07-09 19:08 ` Dan Williams 2020-07-09 9:45 ` Matthias Brugger 2020-07-09 19:10 ` Dan Williams 2020-07-10 21:12 ` Andy Lutomirski 2020-07-10 21:46 ` Dan Williams 2020-07-10 21:13 ` Laura Abbott 2020-07-10 21:48 ` Dan Williams 2020-07-11 20:31 ` josh 2020-07-13 4:20 ` Vinod Koul [this message] 2020-07-13 7:49 ` Joerg Roedel 2020-07-13 8:02 ` Takashi Iwai 2020-07-13 8:43 ` Julia Lawall 2020-07-13 9:36 ` Takashi Iwai 2020-07-13 9:39 ` Julia Lawall 2020-07-13 9:44 ` Takashi Iwai 2020-07-13 15:06 ` [Ksummit-discuss] [Tech-board-discuss] " James Bottomley 2020-07-14 4:39 ` [Ksummit-discuss] " josh 2020-07-14 6:43 ` Takashi Iwai 2020-07-17 16:47 ` Andy Lutomirski 2020-07-15 12:19 ` Jani Nikula 2020-07-17 8:36 ` Pavel Machek
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=20200713042043.GN34333@vkoul-mobl \ --to=vkoul@kernel.org \ --cc=James.Bottomley@hansenpartnership.com \ --cc=airlied@redhat.com \ --cc=christian.brauner@ubuntu.com \ --cc=dan.carpenter@oracle.com \ --cc=dan.j.williams@intel.com \ --cc=gregkh@linuxfoundation.org \ --cc=ksummit-discuss@lists.linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=sjpark@amazon.de \ --cc=tech-board-discuss@lists.linuxfoundation.org \ --subject='Re: [Ksummit-discuss] [PATCH v3] CodingStyle: Inclusive Terminology' \ /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
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).