From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, marcin.kraglak@telink-semi.com
Subject: RE: [1/2] shared/util: Add CAS, HAS, TMAS and PBAS UUIDs
Date: Sat, 28 Jan 2023 00:16:41 -0800 (PST) [thread overview]
Message-ID: <63d4d9e9.a70a0220.5ef34.68d5@mx.google.com> (raw)
In-Reply-To: <20230128063733.18131-1-marcin.kraglak@telink-semi.com>
[-- Attachment #1: Type: text/plain, Size: 946 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=716526
---Test result---
Test Summary:
CheckPatch PASS 0.64 seconds
GitLint PASS 0.49 seconds
BuildEll PASS 26.46 seconds
BluezMake PASS 771.91 seconds
MakeCheck PASS 10.72 seconds
MakeDistcheck PASS 147.81 seconds
CheckValgrind PASS 239.91 seconds
CheckSmatch PASS 319.65 seconds
bluezmakeextell PASS 96.13 seconds
IncrementalBuild PASS 1222.26 seconds
ScanBuild PASS 961.02 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-01-28 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 6:37 [PATCH 1/2] shared/util: Add CAS, HAS, TMAS and PBAS UUIDs Marcin Kraglak
2023-01-28 6:37 ` [PATCH 2/2] AUTHORS: Update Marcin's email Marcin Kraglak
2023-01-28 8:16 ` bluez.test.bot [this message]
2023-01-30 21:40 ` [PATCH 1/2] shared/util: Add CAS, HAS, TMAS and PBAS UUIDs patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-01-27 11:35 Marcin Kraglak
2023-01-27 13:29 ` [1/2] " 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=63d4d9e9.a70a0220.5ef34.68d5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcin.kraglak@telink-semi.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.