From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pali@kernel.org
Subject: RE: sap: Improve error messages
Date: Thu, 04 Jun 2020 17:12:45 -0700 (PDT) [thread overview]
Message-ID: <5ed98dfd.1c69fb81.aa9e5.6148@mx.google.com> (raw)
In-Reply-To: <20200604232433.4951-1-pali@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1024 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.
While we are preparing for reviewing the patches, we found the following
issue/warning.
Test Result:
checkpatch Failed
Outputs:
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#8:
bluetoothd[19117]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
- total: 0 errors, 1 warnings, 15 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
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2020-06-05 0:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 23:24 [PATCH] sap: Improve error messages Pali Rohár
2020-06-05 0:12 ` bluez.test.bot [this message]
2020-06-05 0:12 ` bluez.test.bot
2020-06-05 7:14 ` [PATCH] " Luiz Augusto von Dentz
2020-06-12 13:13 ` Pali Rohár
2020-06-15 9:48 ` Szymon Janc
2020-07-16 14:40 ` Pali Rohár
2020-09-29 21:36 ` Pali Rohár
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=5ed98dfd.1c69fb81.aa9e5.6148@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pali@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).