From: Alyssa Rosenzweig <alyssa@rosenzweig.io>
To: linux-doc@vger.kernel.org
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Takashi Iwai" <tiwai@suse.de>,
"Bhaskar Chowdhury" <unixbhaskar@gmail.com>,
"Nícolas F. R. A. Prado" <nfraprado@protonmail.com>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org,
"Alyssa Rosenzweig" <alyssa@rosenzweig.io>
Subject: [PATCH] docs: kernel-hacking: Remove inappropriate text
Date: Fri, 3 Sep 2021 11:18:26 -0400 [thread overview]
Message-ID: <20210903151826.6300-1-alyssa@rosenzweig.io> (raw)
Remove inappropriate sexual (and ableist) text from the locking
documentation, aligning it with the kernel code-of-conduct. As the text
was unrelated to locking, this change streamlines the document and
improves readability.
Signed-off-by: Alyssa Rosenzweig <alyssa@rosenzweig.io>
---
Documentation/kernel-hacking/locking.rst | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/Documentation/kernel-hacking/locking.rst b/Documentation/kernel-hacking/locking.rst
index ed1284c6f078..3e1f71608f11 100644
--- a/Documentation/kernel-hacking/locking.rst
+++ b/Documentation/kernel-hacking/locking.rst
@@ -94,16 +94,10 @@ primitives, but I'll pretend they don't exist.
Locking in the Linux Kernel
===========================
-If I could give you one piece of advice: never sleep with anyone crazier
-than yourself. But if I had to give you advice on locking: **keep it
-simple**.
+If I could give you one piece of advice on locking: **keep it simple**.
Be reluctant to introduce new locks.
-Strangely enough, this last one is the exact reverse of my advice when
-you **have** slept with someone crazier than yourself. And you should
-think about getting a big dog.
-
Two Main Types of Kernel Locks: Spinlocks and Mutexes
-----------------------------------------------------
--
2.30.2
next reply other threads:[~2021-09-03 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 15:18 Alyssa Rosenzweig [this message]
2021-09-03 21:57 ` [PATCH] docs: kernel-hacking: Remove inappropriate text Jonathan Corbet
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=20210903151826.6300-1-alyssa@rosenzweig.io \
--to=alyssa@rosenzweig.io \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nfraprado@protonmail.com \
--cc=tiwai@suse.de \
--cc=unixbhaskar@gmail.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 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).