Message ID | 20250129123330.391567-2-deaner92@yahoo.com (mailing list archive) |
---|---|
State | Accepted |
Commit | a2a245849af8e6368b50efe7ace7d6e3d431f077 |
Headers | show |
Series | Bluetooth: Fix code style warning | expand |
Context | Check | Description |
---|---|---|
tedd_an/pre-ci_am | success | Success |
tedd_an/SubjectPrefix | success | Gitlint PASS |
tedd_an/BuildKernel | success | BuildKernel PASS |
tedd_an/CheckAllWarning | success | CheckAllWarning PASS |
tedd_an/CheckSparse | success | CheckSparse PASS |
tedd_an/BuildKernel32 | success | BuildKernel32 PASS |
tedd_an/TestRunnerSetup | success | TestRunnerSetup PASS |
tedd_an/TestRunner_l2cap-tester | success | TestRunner PASS |
tedd_an/TestRunner_iso-tester | success | TestRunner PASS |
tedd_an/TestRunner_bnep-tester | success | TestRunner PASS |
tedd_an/TestRunner_mgmt-tester | fail | TestRunner_mgmt-tester: Total: 490, Passed: 485 (99.0%), Failed: 1, Not Run: 4 |
tedd_an/TestRunner_rfcomm-tester | success | TestRunner PASS |
tedd_an/TestRunner_sco-tester | success | TestRunner PASS |
tedd_an/TestRunner_ioctl-tester | success | TestRunner PASS |
tedd_an/TestRunner_mesh-tester | success | TestRunner PASS |
tedd_an/TestRunner_smp-tester | success | TestRunner PASS |
tedd_an/TestRunner_userchan-tester | success | TestRunner PASS |
I just realized I did not include a v2 in the title. Should I resubmit the patch with a v2 or a v3?
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=929064 ---Test result--- Test Summary: CheckPatch PENDING 0.24 seconds GitLint PENDING 0.22 seconds SubjectPrefix PASS 0.12 seconds BuildKernel PASS 23.83 seconds CheckAllWarning PASS 26.66 seconds CheckSparse PASS 29.69 seconds BuildKernel32 PASS 23.59 seconds TestRunnerSetup PASS 423.37 seconds TestRunner_l2cap-tester PASS 20.23 seconds TestRunner_iso-tester PASS 27.40 seconds TestRunner_bnep-tester PASS 4.82 seconds TestRunner_mgmt-tester FAIL 119.55 seconds TestRunner_rfcomm-tester PASS 7.49 seconds TestRunner_sco-tester PASS 9.28 seconds TestRunner_ioctl-tester PASS 8.07 seconds TestRunner_mesh-tester PASS 5.93 seconds TestRunner_smp-tester PASS 6.91 seconds TestRunner_userchan-tester PASS 5.00 seconds IncrementalBuild PENDING 0.41 seconds Details ############################## Test: CheckPatch - PENDING Desc: Run checkpatch.pl script Output: ############################## Test: GitLint - PENDING Desc: Run gitlint Output: ############################## Test: TestRunner_mgmt-tester - FAIL Desc: Run mgmt-tester with test-runner Output: Total: 490, Passed: 485 (99.0%), Failed: 1, Not Run: 4 Failed Test Cases LL Privacy - Start Discovery 2 (Disable RL) Failed 0.161 seconds ############################## Test: IncrementalBuild - PENDING Desc: Incremental build with the patches in the series Output: --- Regards, Linux Bluetooth
Hello: This patch was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>: On Wed, 29 Jan 2025 13:33:30 +0100 you wrote: > From: Jeremy Clifton <deaner92@yahoo.com> > > Output of checkpatch shows warning: > drivers/bluetooth/bfusb.c:368: WARNING: braces {} are not necessary > for single statement blocks > > Remove braces for single line statement. > > [...] Here is the summary with links: - Bluetooth: Fix code style warning https://git.kernel.org/bluetooth/bluetooth-next/c/a2a245849af8 You are awesome, thank you!
diff --git a/drivers/bluetooth/bfusb.c b/drivers/bluetooth/bfusb.c index cab93935cc7f..0d6ad50da046 100644 --- a/drivers/bluetooth/bfusb.c +++ b/drivers/bluetooth/bfusb.c @@ -365,9 +365,8 @@ static void bfusb_rx_complete(struct urb *urb) buf += 3; } - if (count < len) { + if (count < len) bt_dev_err(data->hdev, "block extends over URB buffer ranges"); - } if ((hdr & 0xe1) == 0xc1) bfusb_recv_block(data, hdr, buf, len);