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, hadess@hadess.net
Subject: RE: [BlueZ] main.conf: Add comment about LA Audio BAP UUIDs
Date: Thu, 17 Nov 2022 22:04:18 -0800 (PST)	[thread overview]
Message-ID: <63772062.050a0220.77116.6c6d@mx.google.com> (raw)
In-Reply-To: <20221102101224.1463549-1-hadess@hadess.net>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.36 seconds
GitLint                       PASS      0.28 seconds
BuildEll                      PASS      26.57 seconds
BluezMake                     PASS      769.73 seconds
MakeCheck                     PASS      11.05 seconds
MakeDistcheck                 PASS      147.94 seconds
CheckValgrind                 PASS      240.89 seconds
bluezmakeextell               PASS      93.89 seconds
IncrementalBuild              PASS      621.01 seconds
ScanBuild                     PASS      967.70 seconds



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2022-11-18  6:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 10:12 [BlueZ] main.conf: Add comment about LA Audio BAP UUIDs Bastien Nocera
2022-11-02 11:18 ` bluez.test.bot
2022-11-03 20:26 ` Luiz Augusto von Dentz
2022-11-09 15:55   ` Bastien Nocera
2022-11-18  2:31 ` bluez.test.bot
2022-11-18  4:05 ` bluez.test.bot
2022-11-18  4:43 ` bluez.test.bot
2022-11-18  5:13 ` bluez.test.bot
2022-11-18  5:33 ` bluez.test.bot
2022-11-18  6:04 ` bluez.test.bot [this message]
2022-11-19  3:47 ` bluez.test.bot
2022-11-19  5:32 ` 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=63772062.050a0220.77116.6c6d@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=hadess@hadess.net \
    --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