All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_prathm@quicinc.com
Subject: RE: [BlueZ] Fix discoverable property not emitted on updating value to false
Date: Mon, 08 Jul 2024 02:42:12 -0700 (PDT)	[thread overview]
Message-ID: <668bb474.050a0220.4a7f2.6ac0@mx.google.com> (raw)
In-Reply-To: <20240708074024.5300-1-quic_prathm@quicinc.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.44 seconds
GitLint                       PASS      0.30 seconds
BuildEll                      PASS      24.34 seconds
BluezMake                     PASS      1621.73 seconds
MakeCheck                     PASS      13.41 seconds
MakeDistcheck                 PASS      178.61 seconds
CheckValgrind                 PASS      256.14 seconds
CheckSmatch                   PASS      364.50 seconds
bluezmakeextell               PASS      121.98 seconds
IncrementalBuild              PASS      1382.91 seconds
ScanBuild                     PASS      989.57 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-07-08  9:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08  7:40 [PATCH BlueZ] Fix discoverable property not emitted on updating value to false quic_prathm
2024-07-08  9:42 ` bluez.test.bot [this message]
2024-07-08 16:00 ` 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=668bb474.050a0220.4a7f2.6ac0@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=quic_prathm@quicinc.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 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.