Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, NoahWeinberger2003@proton.me
Subject: RE: Bluetooth: btusb_qcom: check reassembly bounds and pull results
Date: Sun, 08 Nov 2026 15:43:50 -0800 (PST)	[thread overview]
Message-ID: <6af10936.8af4976c.3b0cdb.a757@mx.google.com> (raw)
In-Reply-To: <y1Xe58FtZGhXfycy9vp3QaGjUElg-vc5EA5FocwznmudOVTgFiYfbqilI4Lj0CRpayllrrY66pkMv9TlGOeq83VQIdL6PEjDbDIEwi28Yk8=@proton.me>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      2.30 seconds
VerifyFixes                   PASS      0.09 seconds
VerifySignedoff               PASS      0.09 seconds
GitLint                       FAIL      0.26 seconds
SubjectPrefix                 PASS      0.09 seconds
BuildKernel                   PASS      30.76 seconds
CheckAllWarning               PASS      34.87 seconds
CheckSparse                   PASS      37.50 seconds
BuildKernel32                 PASS      30.68 seconds
CheckKernelLLVM               PASS      32.45 seconds
TestRunnerSetup               PASS      745.24 seconds
IncrementalBuild              PASS      28.81 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: btusb_qcom: check reassembly bounds and pull results
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#104: 
Affected version/commit: mainline fa4ad798f6f681031775266044ba1b0cf3c670bd (v7.4-rc1, 2026-11-07), drivers/bluetooth/btusb_qcom.c:4387-4462 (recv_intr), 2624-2628 (recv_vendor_pkt), 4258-4262 (send_frame).

WARNING: Reported-by: should be immediately followed by Closes: or Link: with a URL to the report
#114: 
Reported-by: Noah Weinberger <noahweinberger2003@proton.me>


ERROR: Missing Signed-off-by: line(s)

total: 1 errors, 2 warnings, 42 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.

/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14962631.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.


##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: btusb_qcom: check reassembly bounds and pull results

1: CC1 Body does not contain a 'Signed-off-by' line
25: B1 Line exceeds max length (205>80): "Affected version/commit: mainline fa4ad798f6f681031775266044ba1b0cf3c670bd (v7.4-rc1, 2026-11-07), drivers/bluetooth/btusb_qcom.c:4387-4462 (recv_intr), 2624-2628 (recv_vendor_pkt), 4258-4262 (send_frame)."
29: B1 Line exceeds max length (124>80): "mainline fa4ad798f6f681031775266044ba1b0cf3c670bd (v7.4-rc1, 2026-11-07); every code path cited below was re-verified by the"


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

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-11-08 23:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-08 22:32 [PATCH] Bluetooth: btusb_qcom: check reassembly bounds and pull results Noah Weinberger
2026-11-08 23:43 ` 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=6af10936.8af4976c.3b0cdb.a757@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=NoahWeinberger2003@proton.me \
    --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