From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/4] shared/util: Add util_debug_{tlv, bit} helpers
Date: Wed, 18 Oct 2023 15:07:38 -0700 (PDT) [thread overview]
Message-ID: <6530572a.d40a0220.d52be.226c@mx.google.com> (raw)
In-Reply-To: <20231018195653.2532882-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2711 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=794477
---Test result---
Test Summary:
CheckPatch PASS 2.83 seconds
GitLint PASS 1.34 seconds
BuildEll PASS 29.80 seconds
BluezMake PASS 1041.66 seconds
MakeCheck PASS 12.51 seconds
MakeDistcheck PASS 181.54 seconds
CheckValgrind PASS 281.03 seconds
CheckSmatch WARNING 379.25 seconds
bluezmakeextell PASS 121.31 seconds
IncrementalBuild PASS 3585.54 seconds
ScanBuild WARNING 1135.29 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/att.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.monitor/packet.c:1859:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3606:52: warning: array of flexible structuresmonitor/bt.h:3594:40: warning: array of flexible structures
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
In file included from tools/mesh-gatt/crypto.c:32:
./src/shared/util.h:221:9: warning: 1st function call argument is an uninitialized value
return be32_to_cpu(get_unaligned((const uint32_t *) ptr));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./src/shared/util.h:33: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:231:9: warning: 1st function call argument is an uninitialized value
return be64_to_cpu(get_unaligned((const uint64_t *) ptr));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./src/shared/util.h:34: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
prev parent reply other threads:[~2023-10-18 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 19:56 [PATCH BlueZ 1/4] shared/util: Add util_debug_{tlv, bit} helpers Luiz Augusto von Dentz
2023-10-18 19:56 ` [PATCH BlueZ 2/4] monitor: Make use of util_debug_tlv to decode TLV entries Luiz Augusto von Dentz
2023-10-18 19:56 ` [PATCH BlueZ 3/4] shared/bap: Add debug helpers Luiz Augusto von Dentz
2023-10-18 19:56 ` [PATCH BlueZ 4/4] client: Make use of bap-debug functions Luiz Augusto von Dentz
2023-10-18 22:07 ` 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=6530572a.d40a0220.d52be.226c@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 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.