Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, 2122295973@qq.com
Subject: RE: Bluetooth: RFCOMM: hold the listener across child teardown
Date: Sat, 24 Oct 2026 05:04:07 -0700 (PDT)	[thread overview]
Message-ID: <6adc9eb7.4b6e150d.3aa805.71df@mx.google.com> (raw)
In-Reply-To: <tencent_8E1E52CF977BFA4D99F205853D3A71F1D306@qq.com>

[-- Attachment #1: Type: text/plain, Size: 1985 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/series/1192576/

---Test result---

Test Summary:
CheckPatch                    FAIL      0.55 seconds
VerifyFixes                   PASS      0.09 seconds
VerifySignedoff               PASS      0.09 seconds
GitLint                       PASS      0.24 seconds
SubjectPrefix                 PASS      0.08 seconds
BuildKernel                   PASS      22.77 seconds
CheckAllWarning               PASS      26.51 seconds
CheckSparse                   PASS      28.85 seconds
BuildKernel32                 PASS      23.11 seconds
CheckKernelLLVM               PASS      25.68 seconds
TestRunnerSetup               PASS      530.02 seconds
TestRunner_rfcomm-tester      PASS      7.19 seconds
IncrementalBuild              PASS      22.18 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: RFCOMM: hold the listener across child teardown
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 4020751fd0df ("Bluetooth: L2CAP: Hold the listener while notifying child teardown")'
#114: 
Same class as 4020751fd0df (L2CAP) and b4a00dedc5cc (ISO): hold the

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

/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14911944.patch has style problems, please review.

NOTE: Ignored message types: UNKNOWN_COMMIT_ID

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




https://github.com/bluez/bluetooth-next/pull/994

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-10-24 12:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24  8:03 [PATCH] Bluetooth: RFCOMM: hold the listener across child teardown Hang Nan
2026-10-24 12:04 ` bluez.test.bot [this message]

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=6adc9eb7.4b6e150d.3aa805.71df@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=2122295973@qq.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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