On 2024-01-28 14:26, Randy Dunlap wrote:
On 1/8/24 12:22, Yueh-Shun Li wrote:
> In section "18) Don't re-invent the kernel macros" in "Linux kernel
> coding style":
>
> Recommend reusing macros from headers inside include/linux, instead of
> the obsolete i
der files provide macros"
Some macros are intended to use inside the header file only, or are
considered the implementation detail of other facilities. Developers
are expected to determine if a macro is meant to be used outside the
header file.
Signed-off-by: Yueh-Shun Li
again once the change of the untranslated documentation gets
ready.
Best regards,
Shamrock
[1]:
https://lore.kernel.org/linux-doc/bc63acd7ef43bdd8d9609fa48dbf9...@posteo.net/
[2]:
https://lore.kernel.org/linux-doc/107b6b5e-ca14-4b2b-ba2e-38ecd74c0...@infradead.org/
[3]: https://lore.kernel.org/
On 2024-01-09 03:37, Yueh-Shun Li wrote:
Dear Maintainers,
In this version of patch series, I drop the patch abouth the nameing
conflicts caused by locally-defined macro variants to streamline the
documentation.[1]
This series of patches targets the "Linux kernel coding style"
doc
107b6b5e-ca14-4b2b-ba2e-38ecd74c0...@infradead.org/
Yueh-Shun Li (3):
coding-style: recommend split headers instead of kernel.h
doc/zh_TW: coding-style: update content for section 18
doc/zh_CN: coding-style: update content of section 18
Documentation/process/coding-style.rst| 24 +
Dear Mr. Corbet,
Thank you very much for your feed back.
On 2024-01-09 00:28, Jonathan Corbet wrote:
Yueh-Shun Li writes:
In section "18) Don't re-invent the kernel macros" in "Linux kernel
coding style":
Show how reusing macros from shared headers prevent
e a stronger reason to reuse shared macros,
by showing the risk of improvised macro variants.
Signed-off-by: Yueh-Shun Li
---
Documentation/process/coding-style.rst | 22 ++
1 file changed, 22 insertions(+)
diff --git a/Documentation/process/coding-style.rst
b/Documenta
der files provide macros"
Some macros are intended to use inside the header file only, or are
considered the implementation detail of other facilities. Developers
are expected to determine if a macro is meant to be used outside the
header file.
Signed-off-by: Yueh-Shun Li
rnel.org/linux-doc/bc63acd7ef43bdd8d9609fa48dbf9...@posteo.net/
[2]:
https://lore.kernel.org/linux-doc/107b6b5e-ca14-4b2b-ba2e-38ecd74c0...@infradead.org/
Yueh-Shun Li (4):
coding-style: recommend split headers instead of kernel.h
coding-style: show how reusing macros prevents naming collisions
