Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, cochcoder@proton.me
Subject: RE: [RFC,v6,1/2] Bluetooth: L2CAP: Keep credits from completing security upgrades
Date: Fri, 06 Nov 2026 14:54:22 -0800 (PST)	[thread overview]
Message-ID: <6aee5a9e.ccc6ed06.248315.5e28@mx.google.com> (raw)
In-Reply-To: <20261106173948.596166-1-cochcoder@proton.me>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      2.10 seconds
VerifyFixes                   PASS      0.07 seconds
VerifySignedoff               PASS      0.07 seconds
GitLint                       PASS      0.59 seconds
SubjectPrefix                 PASS      0.13 seconds
BuildKernel                   PASS      32.44 seconds
CheckAllWarning               PASS      36.82 seconds
CheckSparse                   PASS      39.32 seconds
BuildKernel32                 PASS      32.47 seconds
CheckKernelLLVM               PASS      35.58 seconds
TestRunnerSetup               PASS      760.04 seconds
TestRunner_l2cap-tester       PASS      12.91 seconds
TestRunner_smp-tester         PASS      4.42 seconds
IncrementalBuild              PASS      43.00 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[RFC,v6,1/2] Bluetooth: L2CAP: Keep credits from completing security upgrades
WARNING: Non-standard signature: Assisted-by:
#106: 
Assisted-by: LLM

ERROR: Unrecognized email address: 'LLM'
#106: 
Assisted-by: LLM

total: 1 errors, 1 warnings, 0 checks, 452 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/14958622.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.


[RFC,v6,2/2] Bluetooth: L2CAP: tolerate zero-ident LE credit indications
WARNING: Non-standard signature: Assisted-by:
#102: 
Assisted-by: LLM

ERROR: Unrecognized email address: 'LLM'
#102: 
Assisted-by: LLM

total: 1 errors, 1 warnings, 0 checks, 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.

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

---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2026-11-06 22:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  3:19 [RFC PATCH] Bluetooth: L2CAP: tolerate zero-ident LE credit indications Kyle Pepper
2026-10-13  4:20 ` [RFC] " bluez.test.bot
2026-10-13 14:43 ` [RFC PATCH] " Luiz Augusto von Dentz
2026-10-15 18:31   ` cochcoder
2026-10-15  5:28 ` [RFC PATCH v2] " Kyle Pepper
2026-10-15  6:42   ` [RFC,v2] " bluez.test.bot
2026-10-15 18:16   ` [RFC PATCH v3 1/2] Bluetooth: L2CAP: Keep credits from completing security upgrades Kyle Pepper
2026-10-15 18:17     ` [RFC PATCH v3 2/2] Bluetooth: L2CAP: tolerate zero-ident LE credit indications Kyle Pepper
2026-10-15 20:17     ` [RFC,v3,1/2] Bluetooth: L2CAP: Keep credits from completing security upgrades bluez.test.bot
2026-10-31 18:09     ` [RFC PATCH v3 1/2] " cochcoder
2026-11-06  2:17     ` [RFC PATCH v4 " Kyle Pepper
2026-11-06  2:18       ` [RFC PATCH v4 2/2] Bluetooth: L2CAP: tolerate zero-ident LE credit indications Kyle Pepper
2026-11-06  3:17       ` [RFC,v4,1/2] Bluetooth: L2CAP: Keep credits from completing security upgrades bluez.test.bot
2026-11-06  4:55       ` [RFC PATCH v5 1/2] " Kyle Pepper
2026-11-06  4:56         ` [RFC PATCH v5 2/2] Bluetooth: L2CAP: tolerate zero-ident LE credit indications Kyle Pepper
2026-11-06 16:30           ` Luiz Augusto von Dentz
2026-11-06 10:40         ` [RFC,v5,1/2] Bluetooth: L2CAP: Keep credits from completing security upgrades bluez.test.bot
2026-11-06 17:40         ` [RFC PATCH v6 1/2] " Kyle Pepper
2026-11-06 17:40           ` [RFC PATCH v6 2/2] Bluetooth: L2CAP: tolerate zero-ident LE credit indications Kyle Pepper
2026-11-06 22:54           ` bluez.test.bot [this message]
2026-11-07  2:36           ` [RFC PATCH v7 1/2] Bluetooth: L2CAP: Keep credits from completing security upgrades Kyle Pepper
2026-11-07  2:36             ` [RFC PATCH v7 2/2] Bluetooth: L2CAP: tolerate zero-ident LE credit indications Kyle Pepper
2026-11-07  7:16             ` [RFC PATCH v8 1/2] Bluetooth: L2CAP: Keep credits from completing security upgrades Kyle Pepper
2026-11-07  7:17               ` [RFC PATCH v8 2/2] Bluetooth: L2CAP: tolerate zero-ident LE credit indications Kyle Pepper
2026-11-07  8:32               ` [RFC,v8,1/2] Bluetooth: L2CAP: Keep credits from completing security upgrades 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=6aee5a9e.ccc6ed06.248315.5e28@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=cochcoder@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