From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ] shared/bap: Fix parsing of vendor specific codecs
Date: Tue, 27 Jun 2023 12:51:13 -0700 (PDT) [thread overview]
Message-ID: <649b3db1.050a0220.84e13.b1aa@mx.google.com> (raw)
In-Reply-To: <20230627183446.2488049-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 947 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=760713
---Test result---
Test Summary:
CheckPatch PASS 0.57 seconds
GitLint PASS 0.38 seconds
BuildEll PASS 33.24 seconds
BluezMake PASS 991.55 seconds
MakeCheck PASS 13.32 seconds
MakeDistcheck PASS 189.82 seconds
CheckValgrind PASS 309.51 seconds
CheckSmatch PASS 409.12 seconds
bluezmakeextell PASS 125.85 seconds
IncrementalBuild PASS 818.43 seconds
ScanBuild PASS 1297.89 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-06-27 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 18:34 [PATCH BlueZ] shared/bap: Fix parsing of vendor specific codecs Luiz Augusto von Dentz
2023-06-27 19:50 ` patchwork-bot+bluetooth
2023-06-27 19:51 ` 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=649b3db1.050a0220.84e13.b1aa@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 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).