From: Emil Velikov Date: Wed, 28 Jan 2026 19:56:10 +0000 (+0000) Subject: CODING-STYLE.md: trim down the inspiration section X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=43581736e09c71f0e13211ce82798c835446f345;p=thirdparty%2Fkmod.git CODING-STYLE.md: trim down the inspiration section Omit nearly everything but the projects which serve as inspiration and the associated (updated) Linux kernel style guide link. The checkpatch references are not particularly useful - the tool exists in another (massive) git repo, plus we're using clang-format. Plus the line wrapping details are already listed a few lines below. Signed-off-by: Emil Velikov Reviewed-by: Lucas De Marchi Link: https://github.com/kmod-project/kmod/pull/pull/417 Signed-off-by: Lucas De Marchi --- diff --git a/CODING-STYLE.md b/CODING-STYLE.md index 52290c8e..c8a2c3c8 100644 --- a/CODING-STYLE.md +++ b/CODING-STYLE.md @@ -16,15 +16,8 @@ ASAP. # Inspiration -First of all, kmod coding style must follow every rule for [Linux kernel]. There also exists a tool -named `checkpatch.pl` to help you check the compliance with it. Just type -"checkpatch.pl --no-tree patch_name" to check your patch. In theory, you need -to clean up all the warnings and errors. In certain circumstances one can ignore -the 80 character per line limit. This is generally only allowed if the -alternative would make the code even less readable. - -Besides the kernel coding style above, kmod coding style is heavily based on -oFono's and BlueZ's. Below some basic rules: +The kmod coding style is heavily based on the [Linux kernel]'s, oFono's and +BlueZ's. Below some basic rules: ## Line wrap @@ -90,4 +83,4 @@ Let the includes in the following order, separated by a new line: < tool > "local headers" -[Linux Kernel]: http://www.kernel.org/doc/Documentation/CodingStyle +[Linux Kernel]: https://www.kernel.org/doc/html/v6.9/process/coding-style.html