All of lore.kernel.org
 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] client/player: Split unicast and broadcast presets
Date: Tue, 12 Mar 2024 10:03:37 -0700 (PDT)	[thread overview]
Message-ID: <65f08ae9.050a0220.1e8c0.e965@mx.google.com> (raw)
In-Reply-To: <20240312151740.1105289-1-luiz.dentz@gmail.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=834682

---Test result---

Test Summary:
CheckPatch                    PASS      0.36 seconds
GitLint                       PASS      0.21 seconds
BuildEll                      PASS      23.93 seconds
BluezMake                     PASS      1711.76 seconds
MakeCheck                     PASS      12.78 seconds
MakeDistcheck                 PASS      175.10 seconds
CheckValgrind                 PASS      243.82 seconds
CheckSmatch                   PASS      343.98 seconds
bluezmakeextell               PASS      117.54 seconds
IncrementalBuild              PASS      1424.34 seconds
ScanBuild                     PASS      973.80 seconds



---
Regards,
Linux Bluetooth


      reply	other threads:[~2024-03-12 17:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 15:17 [PATCH BlueZ v1] client/player: Split unicast and broadcast presets Luiz Augusto von Dentz
2024-03-12 17:03 ` 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=65f08ae9.050a0220.1e8c0.e965@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 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.