From ff9f94652aee5a3d9003ba36879559f5e4495b5c Mon Sep 17 00:00:00 2001 From: Michael Brudevold Date: Fri, 3 Jun 2022 16:26:04 -0500 Subject: [PATCH] doc/coding-style: Update URL to kernel coding style Signed-off-by: Manika Shrivastava Signed-off-by: Ayush Garg --- doc/coding-style.txt | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/doc/coding-style.txt b/doc/coding-style.txt index f0bf880..bfe4246 100755 --- a/doc/coding-style.txt +++ b/doc/coding-style.txt @@ -7,14 +7,13 @@ some level of consistency among developers so that code can be easily understood and maintained. First of all, BlueZ coding style must follow every rule for Linux kernel -(http://www.kernel.org/doc/Documentation/CodingStyle). 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 except this one: "ERROR: Missing -Signed-off-by: line(s)". BlueZ does not used Signed-Off lines, so including -them is actually an error. 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. +(https://www.kernel.org/doc/Documentation/process/coding-style.rst). 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 except this one: "ERROR: +including them is actually an error. 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, BlueZ has special flavors for its own. Some of them are mandatory (marked as 'M'), while some others are optional -- 2.7.4