From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: [BlueZ,1/5] lib/uuid: Add BASS UUIDs
Date: Fri, 05 May 2023 03:24:17 -0700 (PDT) [thread overview]
Message-ID: <6454d951.050a0220.cf39a.15fb@mx.google.com> (raw)
In-Reply-To: <20230505082943.92033-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2826 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=745222
---Test result---
Test Summary:
CheckPatch PASS 3.69 seconds
GitLint FAIL 1.98 seconds
BuildEll PASS 27.18 seconds
BluezMake PASS 876.48 seconds
MakeCheck PASS 12.32 seconds
MakeDistcheck PASS 154.47 seconds
CheckValgrind PASS 249.05 seconds
CheckSmatch PASS 338.42 seconds
bluezmakeextell PASS 101.88 seconds
IncrementalBuild PASS 3620.01 seconds
ScanBuild WARNING 1030.84 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,3/5] shared/util: Add iovec helpers for pulling/pushing le32 and le24 values
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
1: T1 Title exceeds max length (83>80): "[BlueZ,3/5] shared/util: Add iovec helpers for pulling/pushing le32 and le24 values"
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
In file included from tools/mesh-gatt/crypto.c:32:
./src/shared/util.h:174:9: warning: 1st function call argument is an uninitialized value
return be32_to_cpu(get_unaligned((const uint32_t *) ptr));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./src/shared/util.h:32:26: note: expanded from macro 'be32_to_cpu'
#define be32_to_cpu(val) bswap_32(val)
^~~~~~~~~~~~~
/usr/include/byteswap.h:34:21: note: expanded from macro 'bswap_32'
#define bswap_32(x) __bswap_32 (x)
^~~~~~~~~~~~~~
In file included from tools/mesh-gatt/crypto.c:32:
./src/shared/util.h:184:9: warning: 1st function call argument is an uninitialized value
return be64_to_cpu(get_unaligned((const uint64_t *) ptr));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./src/shared/util.h:33:26: note: expanded from macro 'be64_to_cpu'
#define be64_to_cpu(val) bswap_64(val)
^~~~~~~~~~~~~
/usr/include/byteswap.h:37:21: note: expanded from macro 'bswap_64'
#define bswap_64(x) __bswap_64 (x)
^~~~~~~~~~~~~~
2 warnings generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-05-05 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 8:29 [PATCH BlueZ 0/5] Add initial code for handling BASS Iulia Tanasescu
2023-05-05 8:29 ` [PATCH BlueZ 1/5] lib/uuid: Add BASS UUIDs Iulia Tanasescu
2023-05-05 10:24 ` bluez.test.bot [this message]
2023-05-05 8:29 ` [PATCH BlueZ 2/5] shared/att-types: Add BT_ERROR_WRITE_REQUEST_REJECTED error code Iulia Tanasescu
2023-05-05 8:29 ` [PATCH BlueZ 3/5] shared/util: Add iovec helpers for pulling/pushing le32 and le24 values Iulia Tanasescu
2023-05-05 8:29 ` [PATCH BlueZ 4/5] shared/bass: Add initial code for handling BASS Iulia Tanasescu
2023-05-05 8:29 ` [PATCH BlueZ 5/5] profiles: Add initial code for BASS plugin Iulia Tanasescu
2023-05-05 18:50 ` [PATCH BlueZ 0/5] Add initial code for handling BASS 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=6454d951.050a0220.cf39a.15fb@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iulia.tanasescu@nxp.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.