From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, uhrmar@gmail.com
Subject: RE: [v2] Add pattern matching for service UUIDs
Date: Sun, 25 Aug 2024 15:42:24 -0700 (PDT) [thread overview]
Message-ID: <66cbb350.c80a0220.257424.c150@mx.google.com> (raw)
In-Reply-To: <20240825205817.70066-1-uhrmar@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 949 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=883075
---Test result---
Test Summary:
CheckPatch PASS 0.49 seconds
GitLint PASS 0.33 seconds
BuildEll PASS 24.72 seconds
BluezMake PASS 1703.42 seconds
MakeCheck PASS 12.88 seconds
MakeDistcheck PASS 181.22 seconds
CheckValgrind PASS 254.17 seconds
CheckSmatch PASS 358.38 seconds
bluezmakeextell PASS 121.75 seconds
IncrementalBuild PASS 1588.75 seconds
ScanBuild PASS 1048.78 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-08-25 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 20:58 [PATCH v2] Add pattern matching for service UUIDs Markus Uhr
2024-08-25 22:42 ` bluez.test.bot [this message]
2024-11-09 9:35 ` Markus Uhr
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=66cbb350.c80a0220.257424.c150@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=uhrmar@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