From: Henrik Grimler <henrik@grimler.se>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ,v3] tools: fix forgotten index->mgmt_index renaming in btmgmt.c
Date: Sat, 10 Oct 2020 09:48:07 +0200 [thread overview]
Message-ID: <81a98880c72ad06b48bc2f25a673e3346fd339d7.camel@grimler.se> (raw)
In-Reply-To: <5f7c9d77.1c69fb81.532c0.5527@mx.google.com>
Hi,
The lint check seem to fail due to long lines in the old code. In the
new code the same lines are shorter than 75 chars.
Is there anything I can do to make the check pass?
Best regards,
Henrik Grimler
On Tue, 2020-10-06 at 09:38 -0700, bluez.test.bot@gmail.com wrote:
> 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=360353
>
> ---Test result---
>
> ##############################
> Test: CheckPatch - FAIL
> Output:
> tools: fix forgotten index->mgmt_index renaming in btmgmt.c
> WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description
> (prefer a maximum 75 chars per line)
> #12:
> config_info_rsp, UINT_TO_PTR(index),
> NULL)) {
>
> - total: 0 errors, 1 warnings, 11 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.
>
> Your patch 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-10-10 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 15:50 [PATCH BlueZ v3] tools: fix forgotten index->mgmt_index renaming in btmgmt.c Henrik Grimler
2020-10-06 16:38 ` [BlueZ,v3] " bluez.test.bot
2020-10-10 7:48 ` Henrik Grimler [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=81a98880c72ad06b48bc2f25a673e3346fd339d7.camel@grimler.se \
--to=henrik@grimler.se \
--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).