From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, marcel@holtmann.org
Subject: RE: doc/mgmt-api.txt: Introduce Set Runtime Firmware command
Date: Tue, 22 Dec 2020 05:45:57 -0800 (PST) [thread overview]
Message-ID: <5fe1f895.1c69fb81.10313.13dc@mx.google.com> (raw)
In-Reply-To: <20201222124651.101063-1-marcel@holtmann.org>
[-- Attachment #1: Type: text/plain, Size: 1807 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=405289
---Test result---
##############################
Test: CheckPatch - FAIL
Output:
doc/mgmt-api.txt: Introduce Set Runtime Firmware command
WARNING:TYPO_SPELLING: 'firwmare' may be misspelled - perhaps 'firmware'?
#37: FILE: doc/mgmt-api.txt:3166:
+ some sort of runtime firmware. Only in the firwmare name
WARNING:TYPO_SPELLING: 'charaters' may be misspelled - perhaps 'characters'?
#38: FILE: doc/mgmt-api.txt:3167:
+ happens to exceed the 255 charaters, the shortened type
WARNING:TYPO_SPELLING: 'firwmare' may be misspelled - perhaps 'firmware'?
#91: FILE: doc/mgmt-api.txt:3910:
+ When the support for runtime firwmare configuration is indicated
- total: 0 errors, 3 warnings, 110 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] doc/mgmt-api.txt: Introduce Set Runtime Firmware command" 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 - FAIL
Output:
doc/mgmt-api.txt: Introduce Set Runtime Firmware command
3: B6 Body message is missing
##############################
Test: CheckBuild - PASS
##############################
Test: MakeCheck - PASS
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2020-12-22 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 12:46 [PATCH] doc/mgmt-api.txt: Introduce Set Runtime Firmware command Marcel Holtmann
2020-12-22 13:45 ` bluez.test.bot [this message]
2020-12-22 19:16 ` Luiz Augusto von Dentz
2020-12-22 21:06 ` Marcel Holtmann
2021-01-11 19:33 ` Abhishek Pandit-Subedi
2021-01-11 21:55 ` Luiz Augusto von Dentz
2021-01-12 18:03 ` Abhishek Pandit-Subedi
2021-01-12 19:37 ` Luiz Augusto von Dentz
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=5fe1f895.1c69fb81.10313.13dc@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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