All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, 20373622@buaa.edu.cn
Subject: RE: [V2] Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security
Date: Tue, 02 Jan 2024 19:56:29 -0800 (PST)	[thread overview]
Message-ID: <6594daed.e90a0220.d653e.363c@mx.google.com> (raw)
In-Reply-To: <20240103031410.3262524-1-20373622@buaa.edu.cn>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.62 seconds
GitLint                       FAIL      0.53 seconds
SubjectPrefix                 PASS      0.13 seconds
BuildKernel                   PASS      28.06 seconds
CheckAllWarning               PASS      30.63 seconds
CheckSparse                   PASS      36.02 seconds
CheckSmatch                   PASS      99.18 seconds
BuildKernel32                 PASS      27.78 seconds
TestRunnerSetup               PASS      435.47 seconds
TestRunner_l2cap-tester       PASS      22.88 seconds
TestRunner_iso-tester         PASS      47.18 seconds
TestRunner_bnep-tester        PASS      6.86 seconds
TestRunner_mgmt-tester        PASS      159.08 seconds
TestRunner_rfcomm-tester      PASS      10.80 seconds
TestRunner_sco-tester         PASS      14.49 seconds
TestRunner_ioctl-tester       PASS      12.05 seconds
TestRunner_mesh-tester        PASS      8.67 seconds
TestRunner_smp-tester         PASS      10.14 seconds
TestRunner_userchan-tester    PASS      7.25 seconds
IncrementalBuild              PASS      26.16 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[V2] Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security

WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
30: B1 Line exceeds max length (81>80): "V1 -> V2: Removed the direct check for `conn` being null in rfcomm_check_security"


---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-01-03  3:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  3:14 [PATCH V2] Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security Yuxuan Hu
2024-01-03  3:56 ` bluez.test.bot [this message]
2024-01-03  8:44 ` Paul Menzel
2024-01-03  9:19   ` Yuxuan-Hu
  -- strict thread matches above, loose matches on Subject: below --
2024-01-03  4:06 Yuxuan Hu
2024-01-03  4:34 ` [V2] " 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=6594daed.e90a0220.d653e.363c@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=20373622@buaa.edu.cn \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.