From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/2] adapter: Fix adding SDP records when operating on LE only mode
Date: Thu, 24 Mar 2022 16:25:02 -0700 (PDT) [thread overview]
Message-ID: <623cfdce.1c69fb81.97131.786f@mx.google.com> (raw)
In-Reply-To: <20220324213658.59479-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1995 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=626167
---Test result---
Test Summary:
CheckPatch FAIL 2.83 seconds
GitLint PASS 1.96 seconds
Prep - Setup ELL PASS 39.94 seconds
Build - Prep PASS 0.74 seconds
Build - Configure PASS 7.92 seconds
Build - Make PASS 1322.38 seconds
Make Check PASS 11.75 seconds
Make Check w/Valgrind PASS 407.79 seconds
Make Distcheck PASS 215.81 seconds
Build w/ext ELL - Configure PASS 8.41 seconds
Build w/ext ELL - Make PASS 1371.63 seconds
Incremental Build with patchesPASS 2697.11 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,2/2] a2dp: Don't initialize a2dp_sep->destroy until properly registered
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#93:
by 0x4A574A8: dbus_connection_dispatch (in /usr/lib64/libdbus-1.so.3.19.14)
/github/workspace/src/12791043.patch total: 0 errors, 1 warnings, 17 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/12791043.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-03-24 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 21:36 [PATCH BlueZ 1/2] adapter: Fix adding SDP records when operating on LE only mode Luiz Augusto von Dentz
2022-03-24 21:36 ` [PATCH BlueZ 2/2] a2dp: Don't initialize a2dp_sep->destroy until properly registered Luiz Augusto von Dentz
2022-03-24 23:25 ` bluez.test.bot [this message]
2022-03-28 18:00 ` [PATCH BlueZ 1/2] adapter: Fix adding SDP records when operating on LE only mode 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=623cfdce.1c69fb81.97131.786f@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).