From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sarveshwar.bajaj@nxp.com
Subject: RE: Fix null pointer dereference in util_ltv_foreach
Date: Fri, 21 Jun 2024 02:47:10 -0700 (PDT) [thread overview]
Message-ID: <66754c1e.170a0220.b0b9.29a1@mx.google.com> (raw)
In-Reply-To: <20240621075517.22576-2-sarveshwar.bajaj@nxp.com>
[-- 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=864176
---Test result---
Test Summary:
CheckPatch PASS 0.32 seconds
GitLint PASS 0.24 seconds
BuildEll PASS 25.08 seconds
BluezMake PASS 1747.58 seconds
MakeCheck PASS 13.12 seconds
MakeDistcheck PASS 186.33 seconds
CheckValgrind PASS 260.03 seconds
CheckSmatch PASS 358.23 seconds
bluezmakeextell PASS 122.82 seconds
IncrementalBuild PASS 1511.84 seconds
ScanBuild PASS 1065.48 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-06-21 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 7:55 [PATCH BlueZ v2 0/1] Fix null pointer dereference in util_ltv_foreach Sarveshwar Bajaj
2024-06-21 7:55 ` [PATCH BlueZ v2 1/1] shared/util: Fix null pointer dereference in util_ltv_foreach() Sarveshwar Bajaj
2024-06-21 9:47 ` bluez.test.bot [this message]
2024-06-25 14:10 ` [PATCH BlueZ v2 0/1] Fix null pointer dereference in util_ltv_foreach patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2024-06-21 6:43 [PATCH BlueZ v2 1/1] shared/util: Fix null pointer dereference in util_ltv_foreach() Sarveshwar Bajaj
2024-06-21 8:42 ` Fix null pointer dereference in util_ltv_foreach 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=66754c1e.170a0220.b0b9.29a1@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sarveshwar.bajaj@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.