From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/4] monitor/att: Print attribute information on ATT_REQ_RSP
Date: Thu, 16 Jun 2022 22:28:48 -0700 (PDT) [thread overview]
Message-ID: <62ac1110.1c69fb81.ebac8.6e90@mx.google.com> (raw)
In-Reply-To: <20220617004957.1148939-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1979 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=651225
---Test result---
Test Summary:
CheckPatch FAIL 6.23 seconds
GitLint PASS 4.01 seconds
Prep - Setup ELL PASS 44.24 seconds
Build - Prep PASS 0.68 seconds
Build - Configure PASS 8.79 seconds
Build - Make PASS 1783.85 seconds
Make Check PASS 11.64 seconds
Make Check w/Valgrind PASS 475.19 seconds
Make Distcheck PASS 244.82 seconds
Build w/ext ELL - Configure PASS 9.09 seconds
Build w/ext ELL - Make PASS 1725.65 seconds
Incremental Build with patchesPASS 7055.43 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,4/4] monitor/att: Add LTV deconding support for PAC/ASE
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#86:
Channel: 65 len 27 sdu 25 [PSM 39 mode Enhanced Credit (0x81)] {chan 1}
/github/workspace/src/12885016.patch total: 0 errors, 1 warnings, 770 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.
/github/workspace/src/12885016.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
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:[~2022-06-17 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 0:49 [PATCH BlueZ 1/4] monitor/att: Print attribute information on ATT_REQ_RSP Luiz Augusto von Dentz
2022-06-17 0:49 ` [PATCH BlueZ 2/4] monitor/att: Add decoding support for PAC Sink/Source Location Luiz Augusto von Dentz
2022-06-17 0:49 ` [PATCH BlueZ 3/4] monitor/att: Add decoding support for PAC Audio Context Luiz Augusto von Dentz
2022-06-17 0:49 ` [PATCH BlueZ 4/4] monitor/att: Add LTV deconding support for PAC/ASE Luiz Augusto von Dentz
2022-06-17 5:28 ` bluez.test.bot [this message]
2022-06-17 21:10 ` [PATCH BlueZ 1/4] monitor/att: Print attribute information on ATT_REQ_RSP patchwork-bot+bluetooth
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=62ac1110.1c69fb81.ebac8.6e90@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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).