From: Manuel Ebner <manuelebnerli@mailbox.org>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>
Cc: Manuel Ebner <manuelebnerli@mailbox.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] docs: automarkup.py: add skipidentifiers
Date: Mon, 24 Aug 2026 09:03:09 +0200 [thread overview]
Message-ID: <20260824070312.332802-2-manuelebnerli@mailbox.org> (raw)
Add skipidentifiers to reduce wrongfully high-lighted (bold) words.
Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
---
Pre-patch discussion:
https://lore.kernel.org/all/bba57d51c72d9387ccef2b5979fa618e980c3ebf.camel@mailbox.org/
---
Documentation/sphinx/automarkup.py | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/sphinx/automarkup.py b/Documentation/sphinx/automarkup.py
index c2227ab0a..8a6174950 100644
--- a/Documentation/sphinx/automarkup.py
+++ b/Documentation/sphinx/automarkup.py
@@ -51,7 +51,10 @@ Skipnames = [ 'for', 'if', 'register', 'sizeof', 'struct', 'unsigned' ]
# when following struct/union/enum/typedef keywords.
# Example: "a simple struct that" in workqueue.rst should not be marked as code.
#
-Skipidentifiers = [ 'that', 'which', 'where', 'whose' ]
+Skipidentifiers = [ 'and', 'are', 'as', 'containing', 'in', 'including',
+ 'is', 'name', 'needs', 'of', 'or', 'pages',
+ 'passed', 'randomization', 'request', 'that',
+ 'to', 'where', 'which', 'whose', 'will' ]
#
# Many places in the docs refer to common system calls. It is
--
2.54.0
next reply other threads:[~2026-08-24 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 7:03 Manuel Ebner [this message]
2026-08-24 17:13 ` [PATCH] docs: automarkup.py: add skipidentifiers Randy Dunlap
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=20260824070312.332802-2-manuelebnerli@mailbox.org \
--to=manuelebnerli@mailbox.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
/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