[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20220729023454.18085-1-longjin@RinGoTek.cn>
Date: Fri, 29 Jul 2022 10:34:54 +0800
From: fslongjin <longjin@...GoTek.cn>
To: corbet@....net, twoerner@...il.com, keescook@...omium.org
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
fslongjin <longjin@...GoTek.cn>
Subject: [PATCH] Documentation: Fixed errors in the title level of coding style documents
In Section 3, `Placing Braces and Spaces`. In the previous document, only
`Spaces` is written in the subtitle without the `Braces`. I think this
may be a format error caused by negligence, so I fixed it.
Signed-off-by: fslongjin <longjin@...GoTek.cn>
---
Documentation/process/coding-style.rst | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst
index 03eb53fd029a..2a26bcb9f391 100644
--- a/Documentation/process/coding-style.rst
+++ b/Documentation/process/coding-style.rst
@@ -120,6 +120,9 @@ that breaks the ability to grep for them.
3) Placing Braces and Spaces
----------------------------
+3.1) Braces
+***********
+
The other issue that always comes up in C styling is the placement of
braces. Unlike the indent size, there are few technical reasons to
choose one placement strategy over the other, but the preferred way, as
@@ -231,7 +234,7 @@ Also, use braces when a loop contains more than a single simple statement:
do_something();
}
-3.1) Spaces
+3.2) Spaces
***********
Linux kernel style for use of spaces depends (mostly) on
--
2.20.1
Powered by blists - more mailing lists