On 11/1/22 14:37, bluez.test.bot@xxxxxxxxx wrote:
This is automated email and please do not reply to this email! Dear submitter, Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series: PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=690839 ---Test result--- Test Summary: CheckPatch PASS 1.01 seconds GitLint PASS 0.86 seconds Prep - Setup ELL PASS 26.44 seconds Build - Prep PASS 0.68 seconds Build - Configure PASS 8.16 seconds Build - Make PASS 723.76 seconds Make Check PASS 10.90 seconds Make Check w/Valgrind PASS 287.82 seconds Make Distcheck PASS 233.70 seconds Build w/ext ELL - Configure PASS 8.17 seconds Build w/ext ELL - Make PASS 83.94 seconds Incremental Build w/ patches PASS 0.00 seconds Scan Build WARNING 476.19 seconds Details ############################## Test: Scan Build - WARNING Desc: Run Scan Build with patches Output: ***************************************************************************** The bugs reported by the scan-build may or may not be caused by your patches. Please check the list and fix the bugs if they are caused by your patch. ***************************************************************************** tools/hciattach_qualcomm.c:218:8: warning: Although the value stored to 'n' is used in the enclosing expression, the value is never actually read from 'n' if ((n = read_hci_event(fd, resp, 100)) < 0) { ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ tools/hciattach_qualcomm.c:253:8: warning: Although the value stored to 'n' is used in the enclosing expression, the value is never actually read from 'n' if ((n = read_hci_event(fd, resp, 100)) < 0) { ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2 warnings generated.
That's unlikely caused by this patch.
