From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brian.gix@intel.com
Subject: RE: [BlueZ,1/2] core: make bt_uuid_hash() portable across archs
Date: Wed, 29 Jun 2022 15:15:53 -0700 (PDT) [thread overview]
Message-ID: <62bccf19.1c69fb81.228f2.089d@mx.google.com> (raw)
In-Reply-To: <20220629194432.20229-1-brian.gix@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2511 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=655155
---Test result---
Test Summary:
CheckPatch FAIL 2.96 seconds
GitLint FAIL 1.97 seconds
Prep - Setup ELL PASS 43.80 seconds
Build - Prep PASS 0.68 seconds
Build - Configure PASS 8.68 seconds
Build - Make PASS 1384.18 seconds
Make Check PASS 11.80 seconds
Make Check w/Valgrind PASS 443.83 seconds
Make Distcheck PASS 232.81 seconds
Build w/ext ELL - Configure PASS 8.71 seconds
Build w/ext ELL - Make PASS 1414.25 seconds
Incremental Build with patchesPASS 2767.06 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,2/2] core: Fix signed vs unsigned compare
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#89: FILE: src/device.c:4091:
+ if ((unsigned)now.tv_sec >= device->name_resolve_failed_time +
/github/workspace/src/12900652.patch total: 0 errors, 1 warnings, 8 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/12900652.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.
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
[BlueZ,1/2] core: make bt_uuid_hash() portable across archs
9: B1 Line exceeds max length (98>80): "src/adapter.c:3617:8: error: cast increases required alignment of target type [-Werror=cast-align]"
[BlueZ,2/2] core: Fix signed vs unsigned compare
9: B1 Line exceeds max length (162>80): "src/device.c:4092:17: error: comparison of integer expressions of different signedness: ‘__time_t’ {aka ‘long int’} and ‘long unsigned int’ [-Werror=sign-compare]"
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-06-29 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 19:44 [PATCH BlueZ 1/2] core: make bt_uuid_hash() portable across archs Brian Gix
2022-06-29 19:44 ` [PATCH BlueZ 2/2] core: Fix signed vs unsigned compare Brian Gix
2022-06-29 21:07 ` Luiz Augusto von Dentz
2022-06-29 22:15 ` 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=62bccf19.1c69fb81.228f2.089d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=brian.gix@intel.com \
--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.