From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: SECURITY: Add top-level security doc
Date: Tue, 25 Aug 2026 02:53:06 -0700 (PDT) [thread overview]
Message-ID: <6a8d6602.d1a89f1f.268970.364c@mx.google.com> (raw)
In-Reply-To: <20260825085714.448937-2-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 988 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=1151364
---Test result---
Test Summary:
CheckPatch PASS 0.85 seconds
GitLint PASS 0.64 seconds
BuildEll PASS 20.40 seconds
BluezMake PASS 572.76 seconds
MakeCheck PASS 19.86 seconds
MakeDistcheck PASS 154.00 seconds
CheckValgrind PASS 225.79 seconds
CheckSmatch PASS 303.88 seconds
bluezmakeextell PASS 97.21 seconds
IncrementalBuild PASS 547.55 seconds
ScanBuild PASS 893.78 seconds
https://github.com/bluez/bluez/pull/2433
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-25 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 8:55 [PATCH 0/2] SECURITY: Add top-level security doc Bastien Nocera
2026-08-25 8:55 ` [PATCH 1/2] " Bastien Nocera
2026-08-25 9:53 ` bluez.test.bot [this message]
2026-08-25 8:55 ` [PATCH 2/2] doc: Remove obsolete security-bugs.rst Bastien Nocera
-- strict thread matches above, loose matches on Subject: below --
2026-08-26 13:19 [BlueZ, v2 1/2] SECURITY: Add top-level security doc Bastien Nocera
2026-08-26 14:33 ` 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=6a8d6602.d1a89f1f.268970.364c@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 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.