All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reuben Varghese <rvarghes@redhat.com>
To: linux-modules@vger.kernel.org
Cc: lucas.de.marchi@gmail.com, yauheni.kaliuta@redhat.com,
	reubenvarghese1 <rvarghes@redhat.com>
Subject: [PATCH v2 2/3] Update documentation reflecting change from blacklist to blocklist
Date: Tue, 18 May 2021 08:03:18 -0700	[thread overview]
Message-ID: <20210518150319.60941-3-rvarghes@redhat.com> (raw)
In-Reply-To: <20210518150319.60941-1-rvarghes@redhat.com>

From: reubenvarghese1 <rvarghes@redhat.com>

With the introduction of inclusive language in the kmod module,
the documentation has been updated in this commit to reflect the
changes made.

Signed-off-by: Reuben Varghese <rvarghes@redhat.com>
---
 man/modprobe.d.xml | 8 ++++++--
 man/modprobe.xml   | 4 ++--
 2 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/man/modprobe.d.xml b/man/modprobe.d.xml
index 0ab3e91..594a847 100644
--- a/man/modprobe.d.xml
+++ b/man/modprobe.d.xml
@@ -98,7 +98,7 @@
         </listitem>
       </varlistentry>
       <varlistentry>
-        <term>blacklist <replaceable>modulename</replaceable>
+        <term>blocklist <replaceable>modulename</replaceable>
         </term>
         <listitem>
           <para>
@@ -107,9 +107,13 @@
             "internal" aliases can be overridden by normal "alias" keywords,
             but there are cases where two or more modules both support the same
             devices, or a module invalidly claims to support a device that it
-            does not: the <command>blacklist</command> keyword indicates that
+            does not: the <command>blocklist</command> keyword indicates that
             all of that particular module's internal aliases are to be ignored.
           </para>
+          <para>
+            Note that the <command>blacklist</command> command is being
+            deprecated and has been refactored to <command>blocklist</command>.
+          </para>
         </listitem>
       </varlistentry>
       <varlistentry>
diff --git a/man/modprobe.xml b/man/modprobe.xml
index 0372b6b..9f4c78e 100644
--- a/man/modprobe.xml
+++ b/man/modprobe.xml
@@ -135,12 +135,12 @@
           <option>-b</option>
         </term>
         <term>
-          <option>--use-blacklist</option>
+          <option>--use-blocklist</option>
         </term>
         <listitem>
           <para>
             This option causes <command>modprobe</command> to apply the
-            <command>blacklist</command> commands in the configuration files
+            <command>blocklist</command> commands in the configuration files
             (if any) to module names as well.  It is usually used by
             <citerefentry>
               <refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum>
-- 
2.27.0


  parent reply	other threads:[~2021-05-18 15:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 10:53 [PATCH 0/2] Introduce inclusive language in kmod Reuben Varghese
2021-05-03 10:53 ` [PATCH 1/2] Refactor all instances of blacklist to blocklist and update documentation Reuben Varghese
2021-05-03 10:53 ` [PATCH 2/2] Continue temporary support for Blacklist command with warnings Reuben Varghese
2021-05-15 22:31 ` [PATCH 0/2] Introduce inclusive language in kmod Lucas De Marchi
2021-05-18 15:03   ` [PATCH v2 0/3] " Reuben Varghese
2021-05-18 15:03     ` [PATCH v2 1/3] Refactor all instances of blacklist to blocklist Reuben Varghese
2021-05-21 21:42       ` Lucas De Marchi
2021-05-18 15:03     ` Reuben Varghese [this message]
2021-05-18 15:03     ` [PATCH v2 3/3] Continue temporary support for Blacklist command Reuben Varghese

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=20210518150319.60941-3-rvarghes@redhat.com \
    --to=rvarghes@redhat.com \
    --cc=linux-modules@vger.kernel.org \
    --cc=lucas.de.marchi@gmail.com \
    --cc=yauheni.kaliuta@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.