All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zijun.hu@oss.qualcomm.com
Subject: RE: [bluez] doc: Add CONFIG_POWER_SEQUENCING to tester.config
Date: Wed, 28 Oct 2026 09:02:20 -0700 (PDT)	[thread overview]
Message-ID: <6ae21c8c.963fedab.2a0d42.475a@mx.google.com> (raw)
In-Reply-To: <20261028-fix_tester_cfg-v1-1-e965db9c3c09@oss.qualcomm.com>

[-- Attachment #1: Type: text/plain, Size: 1208 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/1195485/

---Test result---

Test Summary:
CheckPatch                    PASS      0.34 seconds
GitLint                       FAIL      0.26 seconds
BuildEll                      PASS      13.23 seconds
BluezMake                     PASS      173.70 seconds
MakeCheck                     PASS      13.56 seconds
MakeDistcheck                 PASS      97.68 seconds
CheckValgrind                 PASS      151.07 seconds
CheckSmatch                   PASS      172.52 seconds
bluezmakeextell               PASS      62.23 seconds
TestFunctional                PASS      843.77 seconds
IncrementalBuild              PASS      190.27 seconds
ScanBuild                     PASS      611.85 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[bluez] doc: Add CONFIG_POWER_SEQUENCING to tester.config

32: B2 Line has trailing whitespace: "--  "


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

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-10-28 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 14:18 [PATCH bluez] doc: Add CONFIG_POWER_SEQUENCING to tester.config Zijun Hu
2026-10-28 16:02 ` 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=6ae21c8c.963fedab.2a0d42.475a@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=zijun.hu@oss.qualcomm.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 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.