From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/5] shared/ad: Use util_iov_push_* helpers to generate data
Date: Wed, 12 Jul 2023 15:41:29 -0700 (PDT) [thread overview]
Message-ID: <64af2c19.4a0a0220.fc79b.f013@mx.google.com> (raw)
In-Reply-To: <20230712193854.1862996-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2178 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=765012
---Test result---
Test Summary:
CheckPatch PASS 2.76 seconds
GitLint PASS 1.54 seconds
BuildEll PASS 33.65 seconds
BluezMake PASS 1194.55 seconds
MakeCheck PASS 13.10 seconds
MakeDistcheck PASS 191.75 seconds
CheckValgrind PASS 314.67 seconds
CheckSmatch PASS 435.57 seconds
bluezmakeextell PASS 130.95 seconds
IncrementalBuild PASS 4989.68 seconds
ScanBuild WARNING 1400.37 seconds
Details
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
In file included from tools/mesh-gatt/crypto.c:32:
./src/shared/util.h:191: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:201: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:[~2023-07-12 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 19:38 [PATCH BlueZ 1/5] shared/ad: Use util_iov_push_* helpers to generate data Luiz Augusto von Dentz
2023-07-12 19:38 ` [PATCH BlueZ 2/5] main: Remove DEFAULT_SIRK Luiz Augusto von Dentz
2023-07-12 19:38 ` [PATCH BlueZ 3/5] shared/util: Introduce strisutf8 Luiz Augusto von Dentz
2023-07-12 19:38 ` [PATCH BlueZ 4/5] shared/ad: Make use of util_iov_pull_* to parse data Luiz Augusto von Dentz
2023-07-12 19:38 ` [PATCH BlueZ 5/5] test-eir: Run tests using bt_ad Luiz Augusto von Dentz
2023-07-12 22:41 ` bluez.test.bot [this message]
2023-07-12 22:50 ` [PATCH BlueZ 1/5] shared/ad: Use util_iov_push_* helpers to generate data 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=64af2c19.4a0a0220.fc79b.f013@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).