From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: [BlueZ,v2] shared/gatt-db: Fix munmap_chunk invalid pointer
Date: Fri, 05 Jan 2024 02:29:58 -0800 (PST) [thread overview]
Message-ID: <6597da26.050a0220.bbb3c.1434@mx.google.com> (raw)
In-Reply-To: <20240105091742.146342-1-frederic.danis@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 2067 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=814595
---Test result---
Test Summary:
CheckPatch FAIL 0.83 seconds
GitLint PASS 0.32 seconds
BuildEll PASS 24.16 seconds
BluezMake PASS 697.41 seconds
MakeCheck PASS 11.58 seconds
MakeDistcheck PASS 160.25 seconds
CheckValgrind PASS 222.11 seconds
CheckSmatch PASS 326.66 seconds
bluezmakeextell PASS 106.59 seconds
IncrementalBuild PASS 663.30 seconds
ScanBuild PASS 935.33 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2] shared/gatt-db: Fix munmap_chunk invalid pointer
WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#105: FILE: src/shared/gatt-db.c:366:
+ bt_crypto_gatt_hash(db->crypto, hash.iov, db->last_handle + 1, db->hash);
WARNING:LONG_LINE_COMMENT: line length of 89 exceeds 80 columns
#218: FILE: unit/test-gatt.c:2413:
+ /* test that gatt_db_get_hash is able to manage unordered db and doesn't crash */
/github/workspace/src/src/13511878.patch total: 0 errors, 2 warnings, 163 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/13511878.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
prev parent reply other threads:[~2024-01-05 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 9:17 [PATCH BlueZ v2] shared/gatt-db: Fix munmap_chunk invalid pointer Frédéric Danis
2024-01-05 10:29 ` 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=6597da26.050a0220.bbb3c.1434@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=frederic.danis@collabora.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 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).