From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sathish.narasimman@intel.com
Subject: RE: [1/3] audio/transport: seprate a2dp and bap transport to update volume
Date: Fri, 30 Sep 2022 04:24:05 -0700 (PDT) [thread overview]
Message-ID: <6336d1d5.620a0220.8f30d.2aa8@mx.google.com> (raw)
In-Reply-To: <20220930184954.108937-1-sathish.narasimman@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1052 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=682195
---Test result---
Test Summary:
CheckPatch PASS 2.50 seconds
GitLint PASS 1.47 seconds
Prep - Setup ELL PASS 32.20 seconds
Build - Prep PASS 0.66 seconds
Build - Configure PASS 10.32 seconds
Build - Make PASS 994.72 seconds
Make Check PASS 12.20 seconds
Make Check w/Valgrind PASS 350.89 seconds
Make Distcheck PASS 294.93 seconds
Build w/ext ELL - Configure PASS 10.43 seconds
Build w/ext ELL - Make PASS 102.87 seconds
Incremental Build w/ patches PASS 364.73 seconds
Scan Build PASS 673.99 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-09-30 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 18:49 [PATCH 1/3] audio/transport: seprate a2dp and bap transport to update volume Sathish Narasimman
2022-09-30 10:16 ` Message from the future (wrong date) (was: [PATCH 1/3] audio/transport: seprate a2dp and bap transport to update volume) Paul Menzel
2022-09-30 10:23 ` Sathish Narasimman
2022-09-30 11:24 ` bluez.test.bot [this message]
2022-09-30 17:58 ` [PATCH 1/3] audio/transport: seprate a2dp and bap transport to update volume Luiz Augusto von Dentz
2022-09-30 18:49 ` [PATCH 2/3] shared/vcp: Add callback to update media volume Sathish Narasimman
2022-09-30 18:49 ` [PATCH 3/3] profiles: Register callback function to update volume Sathish Narasimman
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=6336d1d5.620a0220.8f30d.2aa8@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sathish.narasimman@intel.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