All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kevin@simpleble.org
Subject: RE: [v2] Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery
Date: Tue, 27 Oct 2026 14:21:51 -0700 (PDT)	[thread overview]
Message-ID: <6ae115ef.d643d4e7.31f61d.b975@mx.google.com> (raw)
In-Reply-To: <20261027172730.86568-1-kevin@simpleble.org>

[-- Attachment #1: Type: text/plain, Size: 1127 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/1194830/

---Test result---

Test Summary:
CheckPatch                    PASS      0.52 seconds
VerifyFixes                   PASS      0.10 seconds
VerifySignedoff               PASS      0.10 seconds
GitLint                       PASS      0.26 seconds
SubjectPrefix                 PASS      0.10 seconds
BuildKernel                   PASS      19.10 seconds
CheckAllWarning               PASS      29.28 seconds
CheckSparse                   PASS      24.05 seconds
BuildKernel32                 PASS      20.28 seconds
CheckKernelLLVM               PASS      22.09 seconds
TestRunnerSetup               PASS      453.55 seconds
TestRunner_mgmt-tester        PASS      83.31 seconds
TestRunner_mesh-tester        PASS      5.04 seconds
IncrementalBuild              PASS      20.25 seconds



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

---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2026-10-27 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 17:27 [PATCH v2] Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery Kevin Dewald
2026-10-27 17:59 ` Luiz Augusto von Dentz
2026-10-27 21:21 ` 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=6ae115ef.d643d4e7.31f61d.b975@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=kevin@simpleble.org \
    --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.