From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, allenwebb@google.com
Subject: RE: Fix git lint error
Date: Thu, 01 Dec 2022 10:49:02 -0800 (PST) [thread overview]
Message-ID: <6388f71e.620a0220.7b7f.74ce@mx.google.com> (raw)
In-Reply-To: <20221201171613.1819631-2-allenwebb@google.com>
[-- Attachment #1: Type: text/plain, Size: 893 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=700921
---Test result---
Test Summary:
CheckPatch PASS 0.35 seconds
GitLint PASS 0.26 seconds
BuildEll PASS 34.37 seconds
BluezMake PASS 1186.40 seconds
MakeCheck PASS 13.08 seconds
MakeDistcheck PASS 189.04 seconds
CheckValgrind PASS 306.64 seconds
bluezmakeextell PASS 124.33 seconds
IncrementalBuild PASS 986.86 seconds
ScanBuild PASS 1316.16 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-12-01 18:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 16:09 [PATCH BlueZ 0/1] bluetooth.ver: Export sanitizer symbols Allen Webb
2022-12-01 16:09 ` [PATCH BlueZ 1/1] " Allen Webb
2022-12-01 16:15 ` [PATCH BlueZ v2 0/1] Add missing sanitizers Allen Webb
2022-12-01 16:15 ` [PATCH BlueZ v2 1/1] bluetooth.ver: Export sanitizer symbols Allen Webb
2022-12-01 17:11 ` Add missing sanitizers bluez.test.bot
2022-12-01 17:13 ` bluetooth.ver: Export sanitizer symbols bluez.test.bot
2022-12-01 17:16 ` [PATCH BlueZ v3 0/1] Fix git lint error Allen Webb
2022-12-01 17:16 ` [PATCH BlueZ v3 1/1] bluetooth.ver: Export sanitizer symbols Allen Webb
2022-12-01 17:44 ` Paul Menzel
2022-12-01 18:46 ` [PATCH BlueZ v4 0/1] Fix spelling error in the commit message Allen Webb
2022-12-01 18:48 ` [PATCH BlueZ v4 1/1] bluetooth.ver: Export sanitizer symbols Allen Webb
2022-12-01 20:06 ` Fix spelling error in the commit message bluez.test.bot
2022-12-01 18:49 ` 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=6388f71e.620a0220.7b7f.74ce@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=allenwebb@google.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).