public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, agarrigues@riseup.net
Subject: RE: drivers: bluetooth: fix uninitialized scalar variable
Date: Sat, 25 Apr 2026 10:25:57 -0700 (PDT)	[thread overview]
Message-ID: <69ecf925.050a0220.f32ef.65ff@mx.google.com> (raw)
In-Reply-To: <aezuBuQca26r4a7l@lal>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.57 seconds
GitLint                       PASS      0.25 seconds
SubjectPrefix                 FAIL      0.08 seconds
BuildKernel                   PASS      27.12 seconds
CheckAllWarning               PASS      29.39 seconds
CheckSparse                   PASS      28.56 seconds
BuildKernel32                 PASS      26.28 seconds
TestRunnerSetup               PASS      567.61 seconds
IncrementalBuild              PASS      24.54 seconds

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


https://github.com/bluez/bluetooth-next/pull/125

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-04-25 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-25 16:38 [PATCH] drivers: bluetooth: fix uninitialized scalar variable Alonso Garrigues
2026-04-25 17:25 ` 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=69ecf925.050a0220.f32ef.65ff@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=agarrigues@riseup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox