[2/3] Test patch #2: CODE_INDENT, LEADING_SPACE

Commit Message

Tedd Ho-Jeong An April 24, 2020, 11:10 p.m. UTC

DO NOT MERGE

Test patch #2
---
 tools/btpclient.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

[e-mail] April 25, 2020, 2:35 a.m. UTC | #1

This is automated email and please do not replay to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
While we are preparing for reviewing the patches, we found the following
issue/warning.


Test Result:
Checkpatch Failed

Patch Title:
[2/3] Test patch #2: CODE_INDENT, LEADING_SPACE

Output:
ERROR:CODE_INDENT: code indent should use tabs where possible
#19: FILE: tools/btpclient.c:65:
+        struct l_queue *devices;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#19: FILE: tools/btpclient.c:65:
+        struct l_queue *devices;$

- total: 1 errors, 1 warnings, 8 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

NOTE: Whitespace errors detected.
      You may wish to use scripts/cleanpatch or scripts/cleanfile

Your patch has style problems, please review.

NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPLIT_STRING

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.



For more details about BlueZ coding style guide, please find it
in doc/coding-style.txt

---
Regards,
Linux Bluetooth

Patch

diff --git a/tools/btpclient.c b/tools/btpclient.c
index aa8a2bae4..7248acc2a 100644
--- a/tools/btpclient.c
+++ b/tools/btpclient.c
@@ -62,7 +62,7 @@  struct btp_adapter {
 	uint32_t supported_settings;
 	uint32_t current_settings;
 	uint32_t default_settings;
-	struct l_queue *devices;
+        struct l_queue *devices;
 };
 
 struct btp_device {