From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, 2965346066@qq.com
Subject: RE: obexd/bip: Fix uninitialized memory and malformed XML in GetImage request
Date: Sun, 22 Mar 2026 18:49:10 -0700 (PDT) [thread overview]
Message-ID: <69c09c16.050a0220.284365.e7ae@mx.google.com> (raw)
In-Reply-To: <tencent_855A3D40BA68914559569DE8F0A84AC00C09@qq.com>
[-- Attachment #1: Type: text/plain, Size: 1311 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=1070581
---Test result---
Test Summary:
CheckPatch PENDING 0.32 seconds
GitLint PENDING 0.34 seconds
BuildEll PASS 21.48 seconds
BluezMake PASS 647.72 seconds
MakeCheck PASS 19.02 seconds
MakeDistcheck PASS 255.04 seconds
CheckValgrind PASS 302.62 seconds
CheckSmatch PASS 364.95 seconds
bluezmakeextell PASS 186.61 seconds
IncrementalBuild PENDING 0.32 seconds
ScanBuild PASS 1043.65 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
https://github.com/bluez/bluez/pull/1983/checks
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-03-23 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 0:48 [PATCH] obexd/bip: Fix uninitialized memory and malformed XML in GetImage request maxing
2026-03-23 1:49 ` bluez.test.bot [this message]
2026-03-24 8:41 ` Bastien Nocera
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=69c09c16.050a0220.284365.e7ae@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=2965346066@qq.com \
--cc=linux-bluetooth@vger.kernel.org \
/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