From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/4] util: Add UTIL_IOV_INIT
Date: Mon, 29 Jan 2024 15:04:29 -0800 (PST) [thread overview]
Message-ID: <65b82efd.050a0220.1196e.f8cc@mx.google.com> (raw)
In-Reply-To: <20240129212036.163298-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2176 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=821071
---Test result---
Test Summary:
CheckPatch PASS 6.40 seconds
GitLint PASS 1.31 seconds
BuildEll PASS 23.90 seconds
BluezMake PASS 705.38 seconds
MakeCheck PASS 11.31 seconds
MakeDistcheck PASS 166.06 seconds
CheckValgrind PASS 226.45 seconds
CheckSmatch PASS 332.44 seconds
bluezmakeextell PASS 107.91 seconds
IncrementalBuild PASS 2677.89 seconds
ScanBuild WARNING 963.25 seconds
Details
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
In file included from tools/mesh-gatt/crypto.c:32:
./src/shared/util.h:236: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:246: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
next prev parent reply other threads:[~2024-01-29 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 21:20 [PATCH BlueZ v1 1/4] util: Add UTIL_IOV_INIT Luiz Augusto von Dentz
2024-01-29 21:20 ` [PATCH BlueZ v1 2/4] client/player: Add metadata support to struct capabilities Luiz Augusto von Dentz
2024-01-29 21:20 ` [PATCH BlueZ v1 3/4] client/player: Use util_iov_dup/util_iov_free whenever possible Luiz Augusto von Dentz
2024-01-29 21:20 ` [PATCH BlueZ v1 4/4] client/player: Add .name field to struct capabilities Luiz Augusto von Dentz
2024-01-29 23:04 ` bluez.test.bot [this message]
2024-01-30 18:40 ` [PATCH BlueZ v1 1/4] util: Add UTIL_IOV_INIT 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=65b82efd.050a0220.1196e.f8cc@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 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).