linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: Propagate disconnection reason
Date: Tue, 20 May 2025 10:58:39 -0700 (PDT)	[thread overview]
Message-ID: <682cc2cf.050a0220.3c32b7.e1d4@mx.google.com> (raw)
In-Reply-To: <20250520162621.190769-2-frederic.danis@collabora.com>

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

---Test result---

Test Summary:
CheckPatch                    PENDING   0.27 seconds
GitLint                       PENDING   0.28 seconds
BuildEll                      PASS      19.94 seconds
BluezMake                     PASS      2553.76 seconds
MakeCheck                     PASS      20.74 seconds
MakeDistcheck                 PASS      199.00 seconds
CheckValgrind                 PASS      275.54 seconds
CheckSmatch                   PASS      300.86 seconds
bluezmakeextell               PASS      127.42 seconds
IncrementalBuild              PENDING   0.22 seconds
ScanBuild                     PASS      896.76 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2025-05-20 17:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 16:26 [PATCH BlueZ v2 0/3] Propagate disconnection reason Frédéric Danis
2025-05-20 16:26 ` [PATCH BlueZ v2 1/3] src/device: Add Disconnected signal to propagate " Frédéric Danis
2025-05-20 16:41   ` Luiz Augusto von Dentz
2025-05-21  9:02     ` Frédéric Danis
     [not found]     ` <edf37243-acd4-493c-9074-f3bcfe6dc05a@collabora.com>
2025-05-21 20:26       ` Luiz Augusto von Dentz
2025-05-20 17:58   ` bluez.test.bot [this message]
2025-05-20 16:26 ` [PATCH BlueZ v2 2/3] doc/device: Add Disconnected signal Frédéric Danis
2025-05-20 16:26 ` [PATCH BlueZ v2 3/3] client: Display disconnection reason Frédéric Danis
  -- strict thread matches above, loose matches on Subject: below --
2025-05-23  7:26 [PATCH BlueZ v4 1/4] lib/mgmt: Add MGMT_DEV_DISCONN_AUTH_FAILURE define Frédéric Danis
2025-05-23  8:46 ` Propagate disconnection reason bluez.test.bot
2025-05-22 15:49 [PATCH BlueZ v3 1/3] src/device: Add Disconnected signal to propagate " Frédéric Danis
2025-05-22 17:01 ` Propagate " bluez.test.bot
2025-05-19 16:14 [PATCH BlueZ 1/3] src/device: Add Disconnected signal to propagate " Frédéric Danis
2025-05-19 17:56 ` Propagate " 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=682cc2cf.050a0220.3c32b7.e1d4@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=frederic.danis@collabora.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;
as well as URLs for NNTP newsgroup(s).