linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, verdre@v0yd.nl
Subject: RE: Power off HCI devices before rfkilling them
Date: Tue, 02 Jan 2024 06:32:30 -0800 (PST)	[thread overview]
Message-ID: <65941e7e.050a0220.bae9f.536a@mx.google.com> (raw)
In-Reply-To: <20240102133311.6712-2-verdre@v0yd.nl>

[-- Attachment #1: Type: text/plain, Size: 1597 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=813840

---Test result---

Test Summary:
CheckPatch                    PASS      5.24 seconds
GitLint                       PASS      1.32 seconds
SubjectPrefix                 FAIL      0.75 seconds
BuildKernel                   PASS      27.69 seconds
CheckAllWarning               PASS      30.59 seconds
CheckSparse                   PASS      36.30 seconds
CheckSmatch                   PASS      99.67 seconds
BuildKernel32                 PASS      26.96 seconds
TestRunnerSetup               PASS      432.67 seconds
TestRunner_l2cap-tester       PASS      22.79 seconds
TestRunner_iso-tester         PASS      40.66 seconds
TestRunner_bnep-tester        PASS      6.78 seconds
TestRunner_mgmt-tester        PASS      160.29 seconds
TestRunner_rfcomm-tester      PASS      10.76 seconds
TestRunner_sco-tester         PASS      14.47 seconds
TestRunner_ioctl-tester       PASS      11.93 seconds
TestRunner_mesh-tester        PASS      8.73 seconds
TestRunner_smp-tester         PASS      9.68 seconds
TestRunner_userchan-tester    PASS      7.19 seconds
IncrementalBuild              PASS      60.21 seconds

Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject


---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-01-02 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 13:33 [PATCH 0/4] Power off HCI devices before rfkilling them Jonas Dreßler
2024-01-02 13:33 ` [PATCH 1/4] Bluetooth: HCI: Remove HCI_POWER_OFF_TIMEOUT Jonas Dreßler
2024-01-02 14:32   ` bluez.test.bot [this message]
2024-01-02 13:33 ` [PATCH 2/4] Bluetooth: mgmt: Remove leftover queuing of power_off work Jonas Dreßler
2024-01-02 13:33 ` [PATCH 3/4] Bluetooth: HCI: Add new state HCI_POWERING_DOWN Jonas Dreßler
2024-01-02 13:33 ` [PATCH 4/4] hci: Queue a HCI power-off command before rfkilling adapters Jonas Dreßler
  -- strict thread matches above, loose matches on Subject: below --
2024-01-02 18:19 [PATCH v2 1/4] Bluetooth: Remove HCI_POWER_OFF_TIMEOUT Jonas Dreßler
2024-01-02 18:58 ` Power off HCI devices before rfkilling them 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=65941e7e.050a0220.bae9f.536a@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=verdre@v0yd.nl \
    /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;
as well as URLs for NNTP newsgroup(s).