From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [[BlueZ] ] mesh-gatt: Fix JSON files missing from dist
Date: Wed, 14 Feb 2024 09:11:09 -0800 (PST) [thread overview]
Message-ID: <65ccf42d.630a0220.b2b4f.aa5d@mx.google.com> (raw)
In-Reply-To: <20240214155019.325715-1-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 2171 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=826064
---Test result---
Test Summary:
CheckPatch FAIL 0.50 seconds
GitLint PASS 0.22 seconds
BuildEll PASS 24.12 seconds
BluezMake PASS 704.47 seconds
MakeCheck PASS 11.79 seconds
MakeDistcheck PASS 165.83 seconds
CheckValgrind PASS 227.25 seconds
CheckSmatch PASS 330.46 seconds
bluezmakeextell PASS 107.33 seconds
IncrementalBuild PASS 665.70 seconds
ScanBuild PASS 956.84 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[[BlueZ] ] mesh-gatt: Fix JSON files missing from dist
WARNING:BAD_FIXES_TAG: Please use correct Fixes: style 'Fixes: <12 chars of sha1> ("<title line>")' - ie: 'Fixes: ("build: Deprecate meshctl tool")'
#50:
Fixes: 1f6553edd8a5c ("build: Deprecate meshctl tool")
WARNING:UNKNOWN_COMMIT_ID: Unknown commit id '1f6553edd8a5c', maybe rebased or not pulled?
#50:
Fixes: 1f6553edd8a5c ("build: Deprecate meshctl tool")
/github/workspace/src/src/13556710.patch total: 0 errors, 2 warnings, 10 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/src/13556710.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.
Use of uninitialized value $cid in concatenation (.) or string at /usr/bin/checkpatch.pl line 3196.
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2024-02-14 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 15:50 [[BlueZ] ] mesh-gatt: Fix JSON files missing from dist Bastien Nocera
2024-02-14 17:11 ` bluez.test.bot [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=65ccf42d.630a0220.b2b4f.aa5d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hadess@hadess.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.