Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, turbine.bmw@gmail.com
Subject: RE: [BlueZ] mgmt-tester: Add LL Privacy tests for a device's changed IRK
Date: Fri, 23 Oct 2026 22:34:58 -0700 (PDT)	[thread overview]
Message-ID: <6adc4382.a3c0497f.2bbac3.251e@mx.google.com> (raw)
In-Reply-To: <20261024004732.57922-1-turbine.bmw@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1100 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/series/1192482/

---Test result---

Test Summary:
CheckPatch                    PASS      0.42 seconds
GitLint                       FAIL      0.25 seconds
BuildEll                      PASS      12.61 seconds
BluezMake                     PASS      166.23 seconds
CheckSmatch                   PASS      164.60 seconds
bluezmakeextell               PASS      56.19 seconds
TestFunctional                PASS      782.51 seconds
IncrementalBuild              PASS      169.82 seconds
ScanBuild                     PASS      629.23 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ] mgmt-tester: Add LL Privacy tests for a device's changed IRK

23: B2 Line has trailing whitespace: "    "
29: B2 Line has trailing whitespace: "    "


https://github.com/bluez/bluez/pull/2706

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-10-24  5:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24  0:47 [PATCH BlueZ] mgmt-tester: Add LL Privacy tests for a device's changed IRK Brandon Williams
2026-10-24  5:34 ` bluez.test.bot [this message]
2026-10-26 17:23 ` Brandon Williams

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=6adc4382.a3c0497f.2bbac3.251e@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=turbine.bmw@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