From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sonnysasaka@chromium.org
Subject: RE: [BlueZ,v4,1/7] battery: Add the internal Battery API
Date: Mon, 30 Nov 2020 12:32:42 -0800 (PST) [thread overview]
Message-ID: <5fc556ea.1c69fb81.8f41a.a91b@mx.google.com> (raw)
In-Reply-To: <20201130200307.386410-1-sonnysasaka@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 2008 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=393515
---Test result---
##############################
Test: CheckPatch - FAIL
Output:
battery: Add the internal Battery API
ERROR:INITIALISED_STATIC: do not initialise statics to NULL
#71: FILE: src/battery.c:38:
+static struct queue *batteries = NULL;
- total: 1 errors, 0 warnings, 215 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
"[PATCH] battery: Add the internal Battery API" has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
test: Add test app for Battery Provider API
ERROR:EXECUTE_PERMISSIONS: do not set execute permissions for source files
#12: FILE: test/example-battery-provider
- total: 1 errors, 0 warnings, 232 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
"[PATCH] test: Add test app for Battery Provider API" has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: CheckGitLint - PASS
##############################
Test: CheckBuild - PASS
##############################
Test: MakeCheck - PASS
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2020-11-30 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 20:03 [PATCH BlueZ v4 1/7] battery: Add the internal Battery API Sonny Sasaka
2020-11-30 20:03 ` [PATCH BlueZ v4 2/7] profiles/battery: Refactor to use battery library Sonny Sasaka
2020-11-30 20:03 ` [PATCH BlueZ v4 3/7] battery: Add Source property to Battery API Sonny Sasaka
2020-11-30 20:03 ` [PATCH BlueZ v4 4/7] doc: Add Battery Provider API doc Sonny Sasaka
2020-11-30 21:28 ` Luiz Augusto von Dentz
2020-11-30 21:56 ` Sonny Sasaka
2020-11-30 20:03 ` [PATCH BlueZ v4 5/7] test: Add test app for Battery Provider API Sonny Sasaka
2020-11-30 20:03 ` [PATCH BlueZ v4 6/7] adapter: Add a public function to find a device by path Sonny Sasaka
2020-11-30 20:03 ` [PATCH BlueZ v4 7/7] battery: Implement Battery Provider API Sonny Sasaka
2020-11-30 20:32 ` 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=5fc556ea.1c69fb81.8f41a.a91b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sonnysasaka@chromium.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).