From: George Jones <gjones.dev@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Zack Mackintire <zackm@gmail.com>
Subject: [PATCH] doc: fix typo in coding-style documentation (reformat)
Date: Wed, 1 Apr 2026 15:12:10 +0100 [thread overview]
Message-ID: <20260401141212.23955-4-gjones.dev@gmail.com> (raw)
In-Reply-To: <20260401141212.23955-1-gjones.dev@gmail.com>
From: Zack Mackintire <zackm@gmail.com>
Signed-off-by: Zack Mackintire <zackm@gmail.com>
---
Documentation/process/coding-style.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst
index 35b381230f6e..28040b3d0e1a 100644
--- a/Documentation/process/coding-style.rst
+++ b/Documentation/process/coding-style.rst
@@ -719,7 +719,7 @@ re-formatting you may want to take a look at the man page. But
remember: ``indent`` is not a fix for bad programming.
Note that you can also use the ``clang-format`` tool to help you with
-these rules, to quickly re-format parts of your code automatically,
+these rules, to quickly reformat parts of your code automatically,
and to review full files in order to spot coding style mistakes,
typos and possible improvements. It is also handy for sorting ``#includes``,
for aligning variables/macros, for reflowing text and other similar tasks.
--
2.43.0
next prev parent reply other threads:[~2026-04-01 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 14:12 [PATCH] doc: clarify sisfb notes and fix minor wording issues George Jones
2026-04-01 14:12 ` [PATCH] doc: clarify wording for FlashPoint system ordering George Jones
2026-04-01 14:12 ` [PATCH] doc: clarify wording for ntrig sensor disconnect behavior George Jones
2026-04-01 14:12 ` George Jones [this message]
2026-04-01 14:12 ` [PATCH] doc: fix typo in serial-console documentation George Jones
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=20260401141212.23955-4-gjones.dev@gmail.com \
--to=gjones.dev@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=zackm@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