From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, r.smirnov@omp.ru
Subject: RE: [BlueZ] plugins/sixaxis: add NULL check in setup_device()
Date: Thu, 27 Jun 2024 05:07:22 -0700 (PDT) [thread overview]
Message-ID: <667d55fa.050a0220.820f.17d4@mx.google.com> (raw)
In-Reply-To: <20240627103022.51199-1-r.smirnov@omp.ru>
[-- Attachment #1: Type: text/plain, Size: 1519 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=866086
---Test result---
Test Summary:
CheckPatch PASS 0.38 seconds
GitLint FAIL 0.48 seconds
BuildEll PASS 24.64 seconds
BluezMake PASS 1721.32 seconds
MakeCheck PASS 13.36 seconds
MakeDistcheck PASS 177.71 seconds
CheckValgrind PASS 254.35 seconds
CheckSmatch PASS 356.74 seconds
bluezmakeextell PASS 124.26 seconds
IncrementalBuild PASS 1565.98 seconds
ScanBuild PASS 988.32 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ] plugins/sixaxis: add NULL check in setup_device()
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
8: B3 Line contains hard tab characters (\t): " device_new()"
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2024-06-27 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 10:30 [PATCH BlueZ] plugins/sixaxis: add NULL check in setup_device() Roman Smirnov
2024-06-27 12:07 ` 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=667d55fa.050a0220.820f.17d4@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=r.smirnov@omp.ru \
/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