Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/4] emulator/vhci: Add debug messages to error paths
Date: Tue, 05 May 2026 14:53:25 -0700 (PDT)	[thread overview]
Message-ID: <69fa66d5.050a0220.de9b2.9626@mx.google.com> (raw)
In-Reply-To: <20260505204719.1348473-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.97 seconds
GitLint                       PASS      1.46 seconds
BuildEll                      PASS      19.86 seconds
BluezMake                     PASS      611.29 seconds
CheckSmatch                   PASS      322.85 seconds
bluezmakeextell               PASS      167.27 seconds
IncrementalBuild              PASS      612.35 seconds
ScanBuild                     PASS      896.75 seconds



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

---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2026-05-05 21:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 20:47 [PATCH BlueZ v1 1/4] emulator/vhci: Add debug messages to error paths Luiz Augusto von Dentz
2026-05-05 20:47 ` [PATCH BlueZ v1 2/4] emulator/hciemu: " Luiz Augusto von Dentz
2026-05-05 20:47 ` [PATCH BlueZ v1 3/4] tools/gap-tester: Enable hciemu debug output Luiz Augusto von Dentz
2026-05-05 20:47 ` [PATCH BlueZ v1 4/4] tools/userchan-tester: " Luiz Augusto von Dentz
2026-05-05 21:53 ` bluez.test.bot [this message]
2026-05-06 13:30 ` [PATCH BlueZ v1 1/4] emulator/vhci: Add debug messages to error paths patchwork-bot+bluetooth

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=69fa66d5.050a0220.de9b2.9626@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@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