From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, vlad.pruteanu@nxp.com
Subject: RE: bap: Allocate memory for broadcast code
Date: Wed, 19 Jun 2024 05:07:07 -0700 (PDT) [thread overview]
Message-ID: <6672c9eb.050a0220.d24dc.868c@mx.google.com> (raw)
In-Reply-To: <20240619095119.167652-2-vlad.pruteanu@nxp.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=863362
---Test result---
Test Summary:
CheckPatch PASS 0.95 seconds
GitLint PASS 0.67 seconds
BuildEll PASS 24.51 seconds
BluezMake PASS 1675.31 seconds
MakeCheck PASS 13.64 seconds
MakeDistcheck PASS 176.61 seconds
CheckValgrind PASS 250.75 seconds
CheckSmatch PASS 352.42 seconds
bluezmakeextell PASS 119.14 seconds
IncrementalBuild PASS 2986.68 seconds
ScanBuild WARNING 1020.79 seconds
Details
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
In file included from tools/mesh-gatt/crypto.c:32:
./src/shared/util.h:240: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:250: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-06-19 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 9:51 [PATCH BlueZ v2 0/2] bap: Allocate memory for broadcast code Vlad Pruteanu
2024-06-19 9:51 ` [PATCH BlueZ v2 1/2] shared/util: Add util_iov_new function Vlad Pruteanu
2024-06-19 12:07 ` bluez.test.bot [this message]
2024-06-19 9:51 ` [PATCH BlueZ v2 2/2] bap: Use util_iov_new when setting bcode Vlad Pruteanu
2024-06-19 14:10 ` [PATCH BlueZ v2 0/2] bap: Allocate memory for broadcast code patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2024-06-18 8:58 [PATCH BlueZ 1/1] " Vlad Pruteanu
2024-06-18 10:44 ` bluez.test.bot
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=6672c9eb.050a0220.d24dc.868c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vlad.pruteanu@nxp.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.