* [PATCH] Documentation: coding-style: Fix indentation in code-blocks
@ 2024-02-02 23:13 Thorsten Blum
2024-02-05 17:16 ` Jonathan Corbet
0 siblings, 1 reply; 2+ messages in thread
From: Thorsten Blum @ 2024-02-02 23:13 UTC (permalink / raw)
To: Jonathan Corbet
Cc: Federico Vaga, Carlos Bilbao, Avadhut Naik, Alex Shi, Yanteng Si,
Hu Haowen, workflows, linux-doc, linux-kernel, Thorsten Blum
- Remove spaces in C code-blocks to align error labels consistently
- Replace tab characters with spaces in emacs-lisp code blocks
Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
---
Documentation/process/coding-style.rst | 6 +++---
Documentation/translations/it_IT/process/coding-style.rst | 6 +++---
Documentation/translations/sp_SP/process/coding-style.rst | 6 +++---
Documentation/translations/zh_CN/process/coding-style.rst | 4 ++--
Documentation/translations/zh_TW/process/coding-style.rst | 4 ++--
5 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst
index c48382c6b477..c1e070f5c750 100644
--- a/Documentation/process/coding-style.rst
+++ b/Documentation/process/coding-style.rst
@@ -586,9 +586,9 @@ fix for this is to split it up into two error labels ``err_free_bar:`` and
.. code-block:: c
- err_free_bar:
+ err_free_bar:
kfree(foo->bar);
- err_free_foo:
+ err_free_foo:
kfree(foo);
return ret;
@@ -679,7 +679,7 @@ values. To do the latter, you can stick the following in your .emacs file:
(c-offsets-alist . (
(arglist-close . c-lineup-arglist-tabs-only)
(arglist-cont-nonempty .
- (c-lineup-gcc-asm-reg c-lineup-arglist-tabs-only))
+ (c-lineup-gcc-asm-reg c-lineup-arglist-tabs-only))
(arglist-intro . +)
(brace-list-intro . +)
(c . c-lineup-C-comments)
diff --git a/Documentation/translations/it_IT/process/coding-style.rst b/Documentation/translations/it_IT/process/coding-style.rst
index 5f244e16f511..284a75ac19f8 100644
--- a/Documentation/translations/it_IT/process/coding-style.rst
+++ b/Documentation/translations/it_IT/process/coding-style.rst
@@ -575,9 +575,9 @@ due parti ``err_free_bar:`` e ``err_free_foo:``:
.. code-block:: c
- err_free_bar:
+ err_free_bar:
kfree(foo->bar);
- err_free_foo:
+ err_free_foo:
kfree(foo);
return ret;
@@ -671,7 +671,7 @@ segue nel vostro file .emacs:
(c-offsets-alist . (
(arglist-close . c-lineup-arglist-tabs-only)
(arglist-cont-nonempty .
- (c-lineup-gcc-asm-reg c-lineup-arglist-tabs-only))
+ (c-lineup-gcc-asm-reg c-lineup-arglist-tabs-only))
(arglist-intro . +)
(brace-list-intro . +)
(c . c-lineup-C-comments)
diff --git a/Documentation/translations/sp_SP/process/coding-style.rst b/Documentation/translations/sp_SP/process/coding-style.rst
index a0261ba5b902..a37274764371 100644
--- a/Documentation/translations/sp_SP/process/coding-style.rst
+++ b/Documentation/translations/sp_SP/process/coding-style.rst
@@ -604,9 +604,9 @@ Normalmente la solución para esto es dividirlo en dos etiquetas de error
.. code-block:: c
- err_free_bar:
+ err_free_bar:
kfree(foo->bar);
- err_free_foo:
+ err_free_foo:
kfree(foo);
return ret;
@@ -698,7 +698,7 @@ sanos. Para hacer esto último, puede pegar lo siguiente en su archivo
(c-offsets-alist . (
(arglist-close . c-lineup-arglist-tabs-only)
(arglist-cont-nonempty .
- (c-lineup-gcc-asm-reg c-lineup-arglist-tabs-only))
+ (c-lineup-gcc-asm-reg c-lineup-arglist-tabs-only))
(arglist-intro . +)
(brace-list-intro . +)
(c . c-lineup-C-comments)
diff --git a/Documentation/translations/zh_CN/process/coding-style.rst b/Documentation/translations/zh_CN/process/coding-style.rst
index fa28ef0a7fee..3bc2810b151d 100644
--- a/Documentation/translations/zh_CN/process/coding-style.rst
+++ b/Documentation/translations/zh_CN/process/coding-style.rst
@@ -523,9 +523,9 @@ Linux 里这是提倡的做法,因为这样可以很简单的给读者提供
.. code-block:: c
- err_free_bar:
+ err_free_bar:
kfree(foo->bar);
- err_free_foo:
+ err_free_foo:
kfree(foo);
return ret;
diff --git a/Documentation/translations/zh_TW/process/coding-style.rst b/Documentation/translations/zh_TW/process/coding-style.rst
index f11dbb65ca21..c7ac504f6f40 100644
--- a/Documentation/translations/zh_TW/process/coding-style.rst
+++ b/Documentation/translations/zh_TW/process/coding-style.rst
@@ -526,9 +526,9 @@ Linux 裏這是提倡的做法,因爲這樣可以很簡單的給讀者提供
.. code-block:: c
- err_free_bar:
+ err_free_bar:
kfree(foo->bar);
- err_free_foo:
+ err_free_foo:
kfree(foo);
return ret;
--
2.39.2
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] Documentation: coding-style: Fix indentation in code-blocks
2024-02-02 23:13 [PATCH] Documentation: coding-style: Fix indentation in code-blocks Thorsten Blum
@ 2024-02-05 17:16 ` Jonathan Corbet
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Corbet @ 2024-02-05 17:16 UTC (permalink / raw)
To: Thorsten Blum
Cc: Federico Vaga, Carlos Bilbao, Avadhut Naik, Alex Shi, Yanteng Si,
Hu Haowen, workflows, linux-doc, linux-kernel, Thorsten Blum
Thorsten Blum <thorsten.blum@toblux.com> writes:
> - Remove spaces in C code-blocks to align error labels consistently
> - Replace tab characters with spaces in emacs-lisp code blocks
>
> Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
> ---
> Documentation/process/coding-style.rst | 6 +++---
> Documentation/translations/it_IT/process/coding-style.rst | 6 +++---
> Documentation/translations/sp_SP/process/coding-style.rst | 6 +++---
> Documentation/translations/zh_CN/process/coding-style.rst | 4 ++--
> Documentation/translations/zh_TW/process/coding-style.rst | 4 ++--
> 5 files changed, 13 insertions(+), 13 deletions(-)
I have applied this, but I would really rather not see a lot of
white-space patches like this; there are so many ways in which our
documentation could use improvement, and this is pretty far down the
list.
Thanks,
jon
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-02-05 17:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-02-02 23:13 [PATCH] Documentation: coding-style: Fix indentation in code-blocks Thorsten Blum
2024-02-05 17:16 ` Jonathan Corbet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox