From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mikhail.v.gavrilov@gmail.com
Subject: RE: Bluetooth: RFCOMM: defer security confirmation to krfcommd
Date: Wed, 02 Sep 2026 18:55:41 -0700 (PDT) [thread overview]
Message-ID: <6a98d39d.fe89a83f.17deba.71a7@mx.google.com> (raw)
In-Reply-To: <20260902235132.453044-1-mikhail.v.gavrilov@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2233 bytes --]
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=1156570
---Test result---
Test Summary:
CheckPatch PASS 0.68 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.11 seconds
GitLint FAIL 0.26 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 25.32 seconds
CheckAllWarning PASS 27.59 seconds
CheckSparse PASS 26.32 seconds
BuildKernel32 PASS 24.83 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 463.47 seconds
TestRunner_rfcomm-tester PASS 26.17 seconds
IncrementalBuild PASS 24.25 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: RFCOMM: defer security confirmation to krfcommd
85: B3 Line contains hard tab characters (\t): " unsigned short rc_family;"
86: B3 Line contains hard tab characters (\t): " uint8_t rc_bdaddr[6]; /* little endian */"
87: B3 Line contains hard tab characters (\t): " uint8_t rc_channel;"
92: B3 Line contains hard tab characters (\t): " struct sockaddr_rc addr = { .rc_family = AF_BLUETOOTH,"
93: B3 Line contains hard tab characters (\t): " .rc_channel = 1 };"
94: B3 Line contains hard tab characters (\t): " int fd = socket(AF_BLUETOOTH, SOCK_STREAM, BTPROTO_RFCOMM);"
96: B3 Line contains hard tab characters (\t): " memcpy(addr.rc_bdaddr, "\x55\x44\x33\x22\x11\x00", 6);"
97: B3 Line contains hard tab characters (\t): " connect(fd, (struct sockaddr *)&addr, sizeof(addr));"
98: B3 Line contains hard tab characters (\t): " close(fd);"
99: B3 Line contains hard tab characters (\t): " return 0;"
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
https://github.com/bluez/bluetooth-next/pull/693
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-03 1:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 23:51 [PATCH] Bluetooth: RFCOMM: defer security confirmation to krfcommd Mikhail Gavrilov
2026-09-03 1:55 ` bluez.test.bot [this message]
2026-09-03 16:47 ` Pauli Virtanen
2026-09-04 0:55 ` Mikhail Gavrilov
2026-09-04 1:20 ` [PATCH v2] " Mikhail Gavrilov
2026-09-04 5:40 ` [v2] " bluez.test.bot
2026-09-05 11:54 ` [PATCH v2] " Pauli Virtanen
2026-09-05 14:49 ` mikhail.v.gavrilov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a98d39d.fe89a83f.17deba.71a7@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox