From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, r.smirnov@omp.ru
Subject: RE: fix errors found by SVACE static analyzer #3
Date: Tue, 09 Jul 2024 08:11:19 -0700 (PDT) [thread overview]
Message-ID: <668d5317.050a0220.d0726.45f3@mx.google.com> (raw)
In-Reply-To: <20240709120031.105038-2-r.smirnov@omp.ru>
[-- Attachment #1: Type: text/plain, Size: 949 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=869638
---Test result---
Test Summary:
CheckPatch PASS 1.90 seconds
GitLint PASS 1.32 seconds
BuildEll PASS 24.56 seconds
BluezMake PASS 1667.59 seconds
MakeCheck PASS 13.11 seconds
MakeDistcheck PASS 179.03 seconds
CheckValgrind PASS 255.48 seconds
CheckSmatch PASS 357.30 seconds
bluezmakeextell PASS 121.14 seconds
IncrementalBuild PASS 6078.28 seconds
ScanBuild PASS 1030.01 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-07-09 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 12:00 [PATCH BlueZ v1 0/4] fix errors found by SVACE static analyzer #3 Roman Smirnov
2024-07-09 12:00 ` [PATCH BlueZ v1 1/4] health: mcap: add checks for NULL mcap_notify_error() Roman Smirnov
2024-07-09 15:11 ` bluez.test.bot [this message]
2024-07-09 12:00 ` [PATCH BlueZ v1 2/4] shared: prevent dereferencing of NULL pointers Roman Smirnov
2024-07-09 12:00 ` [PATCH BlueZ v1 3/4] settings: limit the string size in load_service() Roman Smirnov
2024-07-09 14:02 ` Luiz Augusto von Dentz
2024-07-09 12:00 ` [PATCH BlueZ v1 4/4] settings: limit the number of chars to be read in gatt_db_load() Roman Smirnov
-- strict thread matches above, loose matches on Subject: below --
2024-07-09 14:35 [PATCH BlueZ v2 1/4] health: mcap: add checks for NULL mcap_notify_error() Roman Smirnov
2024-07-09 18:03 ` fix errors found by SVACE static analyzer #3 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=668d5317.050a0220.d0726.45f3@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=r.smirnov@omp.ru \
/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.