From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: SECURITY: Add top-level security doc
Date: Wed, 26 Aug 2026 07:33:10 -0700 (PDT) [thread overview]
Message-ID: <6a8ef926.7a66ee31.25c7ad.1162@mx.google.com> (raw)
In-Reply-To: <20260826132610.1021538-2-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 989 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=1152091
---Test result---
Test Summary:
CheckPatch PASS 0.79 seconds
GitLint PASS 0.59 seconds
BuildEll PASS 20.92 seconds
BluezMake PASS 614.40 seconds
MakeCheck PASS 18.81 seconds
MakeDistcheck PASS 161.68 seconds
CheckValgrind PASS 236.79 seconds
CheckSmatch PASS 316.47 seconds
bluezmakeextell PASS 103.26 seconds
IncrementalBuild PASS 611.30 seconds
ScanBuild PASS 990.31 seconds
https://github.com/bluez/bluez/pull/2437
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-26 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 13:19 [BlueZ, v2 0/2] SECURITY: Add top-level security doc Bastien Nocera
2026-08-26 13:19 ` [BlueZ, v2 1/2] " Bastien Nocera
2026-08-26 14:33 ` bluez.test.bot [this message]
2026-08-26 13:19 ` [BlueZ, v2 2/2] doc: Remove obsolete security-bugs.rst Bastien Nocera
2026-08-28 15:20 ` [BlueZ, v2 0/2] SECURITY: Add top-level security doc patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2026-08-25 8:55 [PATCH 1/2] " Bastien Nocera
2026-08-25 9:53 ` 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=6a8ef926.7a66ee31.25c7ad.1162@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hadess@hadess.net \
--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