From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wouter@xesxen.nl
Subject: RE: shared/shell: Fix SIGSEGV on invalid input
Date: Wed, 18 Mar 2026 21:24:45 -0700 (PDT) [thread overview]
Message-ID: <69bb7a8d.050a0220.31bcff.da59@mx.google.com> (raw)
In-Reply-To: <20260319021645.2137513-2-wouter@xesxen.nl>
[-- Attachment #1: Type: text/plain, Size: 1671 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=1068955
---Test result---
Test Summary:
CheckPatch PENDING 0.30 seconds
GitLint PENDING 0.36 seconds
BuildEll PASS 21.23 seconds
BluezMake PASS 633.50 seconds
MakeCheck PASS 18.51 seconds
MakeDistcheck PASS 244.32 seconds
CheckValgrind PASS 291.23 seconds
CheckSmatch WARNING 352.53 seconds
bluezmakeextell PASS 181.41 seconds
IncrementalBuild PENDING 0.31 seconds
ScanBuild PASS 1008.74 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
https://github.com/bluez/bluez/pull/1970/checks
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-03-19 4:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 2:16 [PATCH BlueZ 0/1] shared/shell: Fix SIGSEGV on invalid input Wouter
2026-03-19 2:16 ` [PATCH BlueZ 1/1] " Wouter
2026-03-19 4:24 ` bluez.test.bot [this message]
2026-03-19 11:08 ` Bastien Nocera
2026-03-19 11:15 ` Bastien Nocera
2026-03-19 14:10 ` Wouter
-- strict thread matches above, loose matches on Subject: below --
2026-03-19 14:14 [PATCH BlueZ v2 " Wouter
2026-03-19 15:54 ` 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=69bb7a8d.050a0220.31bcff.da59@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=wouter@xesxen.nl \
/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