From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/2] shared/hci: Avoid redundant BPF filter updates on duplicate events
Date: Mon, 08 Jun 2026 15:15:55 -0700 (PDT) [thread overview]
Message-ID: <6a273f1b.d5c1a6d7.14e272.4328@mx.google.com> (raw)
In-Reply-To: <20260608205009.97585-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1118 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=1108111
---Test result---
Test Summary:
CheckPatch PASS 0.99 seconds
GitLint FAIL 0.67 seconds
BuildEll PASS 20.62 seconds
BluezMake PASS 632.10 seconds
CheckSmatch PASS 331.99 seconds
bluezmakeextell PASS 166.70 seconds
IncrementalBuild PASS 640.51 seconds
ScanBuild PASS 948.65 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v1,1/2] shared/hci: Avoid redundant BPF filter updates on duplicate events
1: T1 Title exceeds max length (81>80): "[BlueZ,v1,1/2] shared/hci: Avoid redundant BPF filter updates on duplicate events"
https://github.com/bluez/bluez/pull/2197
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-06-08 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 20:50 [PATCH BlueZ v1 1/2] shared/hci: Avoid redundant BPF filter updates on duplicate events Luiz Augusto von Dentz
2026-06-08 20:50 ` [PATCH BlueZ v1 2/2] shared/hci: Debounce SO_ATTACH_FILTER with timeout_add(0) Luiz Augusto von Dentz
2026-06-08 22:15 ` 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=6a273f1b.d5c1a6d7.14e272.4328@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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