linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v2,1/4] shared/util: Add util_debug_{tlv, bit} helpers
Date: Fri, 20 Oct 2023 13:12:14 -0700 (PDT)	[thread overview]
Message-ID: <6532df1e.050a0220.351c3.42f2@mx.google.com> (raw)
In-Reply-To: <20231020180834.3010421-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=795210

---Test result---

Test Summary:
CheckPatch                    PASS      2.89 seconds
GitLint                       PASS      1.37 seconds
BuildEll                      PASS      29.71 seconds
BluezMake                     PASS      1085.10 seconds
MakeCheck                     PASS      12.59 seconds
MakeDistcheck                 PASS      185.35 seconds
CheckValgrind                 PASS      284.84 seconds
CheckSmatch                   WARNING   377.39 seconds
bluezmakeextell               PASS      122.42 seconds
IncrementalBuild              PASS      3643.09 seconds
ScanBuild                     WARNING   1170.95 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


  parent reply	other threads:[~2023-10-20 20:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 18:08 [PATCH BlueZ v2 1/4] shared/util: Add util_debug_{tlv, bit} helpers Luiz Augusto von Dentz
2023-10-20 18:08 ` [PATCH BlueZ v2 2/4] monitor: Make use of util_debug_tlv to decode TLV entries Luiz Augusto von Dentz
2023-10-20 18:08 ` [PATCH BlueZ v2 3/4] shared/bap: Add debug helpers Luiz Augusto von Dentz
2023-10-20 18:08 ` [PATCH BlueZ v2 4/4] client: Make use of bap-debug functions Luiz Augusto von Dentz
2023-10-20 20:12 ` bluez.test.bot [this message]
2023-10-20 20:50 ` [PATCH BlueZ v2 1/4] shared/util: Add util_debug_{tlv, bit} helpers 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=6532df1e.050a0220.351c3.42f2@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).