From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, nitin.jadhav@nxp.com
Subject: RE: Code handling for VOCS service
Date: Mon, 12 Jun 2023 08:34:24 -0700 (PDT) [thread overview]
Message-ID: <64873b00.0c0a0220.32ace.e50f@mx.google.com> (raw)
In-Reply-To: <20230612133251.194-2-nitin.jadhav@nxp.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=756305
---Test result---
Test Summary:
CheckPatch PASS 2.06 seconds
GitLint PASS 1.07 seconds
BuildEll PASS 27.19 seconds
BluezMake PASS 832.60 seconds
MakeCheck PASS 12.59 seconds
MakeDistcheck PASS 155.45 seconds
CheckValgrind PASS 255.24 seconds
CheckSmatch PASS 341.05 seconds
bluezmakeextell PASS 103.39 seconds
IncrementalBuild PASS 2068.15 seconds
ScanBuild PASS 1044.52 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-06-12 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 13:32 [PATCH BlueZ v5 0/3] Code handling for VOCS service Nitin Jadhav
2023-06-12 13:32 ` [PATCH BlueZ v5 1/3] lib/uuid.h: Add VOCS characteristic uuid(s) Nitin Jadhav
2023-06-12 15:34 ` bluez.test.bot [this message]
2023-06-12 13:32 ` [PATCH BlueZ v5 2/3] shared/vcp: Add initial code for handling VOCS Nitin Jadhav
2023-06-12 13:32 ` [PATCH BlueZ v5 3/3] shared/vcp.c: Make VOCS as an included service of VCS Nitin Jadhav
2023-06-27 18:59 ` Pauli Virtanen
2023-06-27 19:14 ` Luiz Augusto von Dentz
2023-06-13 20:50 ` [PATCH BlueZ v5 0/3] Code handling for VOCS service patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 9:42 [PATCH BlueZ v4 1/3] lib/uuid.h: Add VOCS characteristic uuid(s) Nitin Jadhav
2023-06-09 11:33 ` Code handling for VOCS service bluez.test.bot
2023-06-08 12:09 [PATCH BlueZ v3 1/2] Title: Added initial code for handling VOCS Nitin Jadhav
2023-06-08 13:36 ` Code handling for VOCS service bluez.test.bot
2023-06-08 16:30 ` Luiz Augusto von Dentz
2023-06-07 12:13 [PATCH BlueZ v2 1/2] Added initial code for handling VOCS Nitin Jadhav
2023-06-07 13:37 ` Code handling for VOCS service bluez.test.bot
2023-06-06 12:08 [PATCH BlueZ v1 1/2] Added initial code for handling VOCS NJNXP
2023-06-06 13:31 ` Code handling for VOCS service 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=64873b00.0c0a0220.32ace.e50f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=nitin.jadhav@nxp.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).