All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, baul.lee@xbow.com
Subject: RE: Bluetooth: SCO: fix sco_conn double free on outgoing connect
Date: Sun, 26 Jul 2026 02:55:31 -0700 (PDT)	[thread overview]
Message-ID: <6a65d993.6f91ca5b.260d6e.480c@mx.google.com> (raw)
In-Reply-To: <20260726055431.42350-1-baul.lee@xbow.com>

[-- Attachment #1: Type: text/plain, Size: 2477 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=1134537

---Test result---

Test Summary:
CheckPatch                    FAIL      0.76 seconds
VerifyFixes                   PASS      0.13 seconds
VerifySignedoff               PASS      0.14 seconds
GitLint                       PASS      0.36 seconds
SubjectPrefix                 PASS      0.13 seconds
BuildKernel                   PASS      28.19 seconds
CheckAllWarning               PASS      30.75 seconds
CheckSparse                   PASS      30.22 seconds
BuildKernel32                 PASS      27.15 seconds
CheckKernelLLVM               SKIP      0.00 seconds
TestRunnerSetup               PASS      533.50 seconds
TestRunner_sco-tester         FAIL      35.18 seconds
IncrementalBuild              PASS      27.47 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: SCO: fix sco_conn double free on outgoing connect
WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#142: 
Reported-by: Federico Kirschbaum <federico.kirschbaum@xbow.com>
Reported-by: Baul Lee <baul.lee@xbow.com>

WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#143: 
Reported-by: Baul Lee <baul.lee@xbow.com>
Cc: stable@vger.kernel.org

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

/github/workspace/src/patch/14710765.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.


##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
Total: 30, Passed: 29 (96.7%), Failed: 1, Not Run: 0

Failed Test Cases
SCO Disconnect - Success                             Timed out    2.151 seconds


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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-07-26  9:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-26  5:54 [PATCH] Bluetooth: SCO: fix sco_conn double free on outgoing connect Baul Lee
2026-07-26  9:55 ` bluez.test.bot [this message]
2026-07-26 10:15 ` Pauli Virtanen
2026-07-26 13:37   ` Aldo Ariel Panzardo

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=6a65d993.6f91ca5b.260d6e.480c@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=baul.lee@xbow.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.