Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, joeyli.kernel@gmail.com
Subject: RE: Bluetooth: SMP: Fail if the X coordinate of remote and local public keys are identical
Date: Wed, 21 Oct 2026 05:57:09 -0700 (PDT)	[thread overview]
Message-ID: <6ad8b6a5.2feceb42.42020.6a31@mx.google.com> (raw)
In-Reply-To: <20261021093522.3536051-1-jlee@suse.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      0.55 seconds
VerifyFixes                   PASS      0.12 seconds
VerifySignedoff               PASS      0.11 seconds
GitLint                       FAIL      0.27 seconds
SubjectPrefix                 PASS      0.10 seconds
BuildKernel                   PASS      19.28 seconds
CheckAllWarning               PASS      22.70 seconds
CheckSparse                   PASS      24.06 seconds
BuildKernel32                 PASS      19.64 seconds
CheckKernelLLVM               PASS      20.36 seconds
TestRunnerSetup               PASS      431.11 seconds
TestRunner_smp-tester         PASS      7.00 seconds
IncrementalBuild              PASS      19.39 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: SMP: Fail if the X coordinate of remote and local public keys are identical
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 6d19628f539f ("Bluetooth: SMP: Fail if remote and local public keys are identical")'
#120: 
The 6d19628f539f ("Bluetooth: SMP: Fail if remote and local public keys

WARNING: From:/Signed-off-by: email address mismatch: 'From: Chun-Yi Lee <joeyli.kernel@gmail.com>' != 'Signed-off-by: Chun-Yi Lee <jlee@suse.com>'

total: 1 errors, 1 warnings, 0 checks, 8 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/14904963.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: SMP: Fail if the X coordinate of remote and local public keys are identical

1: T1 Title exceeds max length (86>80): "Bluetooth: SMP: Fail if the X coordinate of remote and local public keys are identical"


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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-10-21 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  9:35 [PATCH] Bluetooth: SMP: Fail if the X coordinate of remote and local public keys are identical Chun-Yi Lee
2026-10-21 12:57 ` bluez.test.bot [this message]
2026-10-21 14:00 ` Luiz Augusto von Dentz
2026-10-23  7:17   ` joeyli

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=6ad8b6a5.2feceb42.42020.6a31@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=joeyli.kernel@gmail.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