Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <5ea3a1e3.1c69fb81.90b5b.08ee@mx.google.com>
Date:   Fri, 24 Apr 2020 19:35:15 -0700 (PDT)
Content-Type: multipart/mixed; boundary="===============3169691382207792878=="
MIME-Version: 1.0
From:   bluez.test.bot@gmail.com
To:     linux-bluetooth@vger.kernel.org, tedd.an@linux.intel.com
Subject: RE: [3/3] Test patch #3: OPEN_BRACE
In-Reply-To: <20200424231026.127164-3-tedd.an@linux.intel.com>
References: <20200424231026.127164-3-tedd.an@linux.intel.com>
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

--===============3169691382207792878==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit


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:
[3/3] Test patch #3: OPEN_BRACE

Output:
ERROR:OPEN_BRACE: that open brace { should be on the previous line
#17: FILE: tools/btpclient.c:230:
 	for (entry = l_queue_get_entries(adapters); entry;
+							entry = entry->next)
+	{

- total: 1 errors, 0 warnings, 9 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.

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

--===============3169691382207792878==--