From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, lukas.funke-oss@weidmueller.com
Subject: RE: [BlueZ] adapter: fix heap corruption during discovery filter parsing
Date: Tue, 07 Nov 2023 04:33:13 -0800 (PST) [thread overview]
Message-ID: <654a2e89.050a0220.76e08.a315@mx.google.com> (raw)
In-Reply-To: <20231107103507.505581-1-lukas.funke-oss@weidmueller.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=799389
---Test result---
Test Summary:
CheckPatch PASS 0.47 seconds
GitLint PASS 0.31 seconds
BuildEll PASS 35.00 seconds
BluezMake PASS 1168.98 seconds
MakeCheck PASS 13.18 seconds
MakeDistcheck PASS 216.18 seconds
CheckValgrind PASS 326.28 seconds
CheckSmatch PASS 451.89 seconds
bluezmakeextell PASS 146.58 seconds
IncrementalBuild PASS 1034.35 seconds
ScanBuild PASS 1419.95 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-11-07 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 10:35 [PATCH BlueZ] adapter: fix heap corruption during discovery filter parsing lukas.funke-oss
2023-11-07 12:33 ` bluez.test.bot [this message]
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=654a2e89.050a0220.76e08.a315@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lukas.funke-oss@weidmueller.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