public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, condorachest@gmail.com
Subject: RE: adapter: add DisableDiscoveryOnConnect option for combo chip coexistence
Date: Sat, 18 Apr 2026 08:47:28 -0700 (PDT)	[thread overview]
Message-ID: <69e3a790.050a0220.382ba.7d0f@mx.google.com> (raw)
In-Reply-To: <20260418141127.243863-1-condorachest@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.50 seconds
GitLint                       PASS      0.34 seconds
BuildEll                      PASS      20.26 seconds
BluezMake                     PASS      609.83 seconds
MakeCheck                     PASS      19.27 seconds
MakeDistcheck                 PASS      236.90 seconds
CheckValgrind                 PASS      277.51 seconds
CheckSmatch                   WARNING   322.18 seconds
bluezmakeextell               PASS      166.35 seconds
IncrementalBuild              PASS      595.91 seconds
ScanBuild                     PASS      922.27 seconds

Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/main.c: note: in included file (through src/device.h):


https://github.com/bluez/bluez/pull/2054

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-04-18 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-18 14:11 [PATCH] adapter: add DisableDiscoveryOnConnect option for combo chip coexistence StefanCondorache
2026-04-18 15:47 ` bluez.test.bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-18 13:27 StefanCondorache
2026-04-18 14:06 ` bluez.test.bot

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=69e3a790.050a0220.382ba.7d0f@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=condorachest@gmail.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