Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org,
	kaihsin.chung@synaptics.corp-partner.google.com
Subject: RE: [v4] Bluetooth: Add Synaptics 4384 Chip Support
Date: Tue, 12 May 2026 21:40:31 -0700 (PDT)	[thread overview]
Message-ID: <6a0400bf.0c0a0220.340460.a21a@mx.google.com> (raw)
In-Reply-To: <20260513022008.3238060-1-kaihsin.chung@synaptics.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.05 seconds
GitLint                       PASS      0.33 seconds
SubjectPrefix                 PASS      0.35 seconds
BuildKernel                   PASS      25.97 seconds
CheckAllWarning               PASS      29.42 seconds
CheckSparse                   PASS      27.85 seconds
BuildKernel32                 PASS      25.96 seconds
TestRunnerSetup               PASS      537.07 seconds
IncrementalBuild              PASS      25.45 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v4] Bluetooth: Add Synaptics 4384 Chip Support
WARNING: DT compatible string "brcm,bcm4384-bt" appears un-documented -- check ./Documentation/devicetree/bindings/
#160: FILE: drivers/bluetooth/hci_bcm.c:1612:
+	{ .compatible = "brcm,bcm4384-bt" },

WARNING: From:/Signed-off-by: email name mismatch: 'From: Kaihsin Chung <kaihsin.chung@synaptics.com>' != 'Signed-off-by: kaihsin Chung <kaihsin.chung@synaptics.com>'

total: 0 errors, 2 warnings, 31 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

/github/workspace/src/patch/14570021.patch has style problems, please review.

NOTE: Ignored message types: UNKNOWN_COMMIT_ID

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.




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

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-05-13  4:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08  8:32 [PATCH] Bluetooth: Add Synaptcis 4384 Chip Support kaihsin
2026-04-08  8:46 ` Paul Menzel
2026-04-08 14:46   ` Luiz Augusto von Dentz
2026-04-08  9:21 ` [PATCH v2] Bluetooth: Add Synaptics " kaihsin Chung
2026-04-08 10:31   ` [v2] " bluez.test.bot
2026-04-08  9:21 ` Bluetooth: Add Synaptcis " bluez.test.bot
2026-04-09  1:30 ` [PATCH v3] Bluetooth: Add Synaptics " kaihsin Chung
2026-04-09 20:19   ` [v3] " bluez.test.bot
2026-04-10 14:16     ` Luiz Augusto von Dentz
2026-04-29  9:32       ` Kaihsin Chung
2026-04-09 20:20 ` Bluetooth: Add Synaptcis " bluez.test.bot
2026-05-13  2:20 ` [PATCH v4] Bluetooth: Add Synaptics " kaihsin Chung
2026-05-13  4:40   ` 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=6a0400bf.0c0a0220.340460.a21a@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=kaihsin.chung@synaptics.corp-partner.google.com \
    --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