All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, horms@kernel.org
Subject: RE: Bluetooth: L2CAP: don't check for out-of-bounds value
Date: Fri, 26 May 2023 07:57:18 -0700 (PDT)	[thread overview]
Message-ID: <6470c8ce.0c0a0220.c4651.7003@mx.google.com> (raw)
In-Reply-To: <20230526-l2cap-16bit-v1-1-2cfb83dd28ee@kernel.org>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.73 seconds
GitLint                       FAIL      0.59 seconds
SubjectPrefix                 PASS      0.13 seconds
BuildKernel                   PASS      32.79 seconds
CheckAllWarning               PASS      35.87 seconds
CheckSparse                   PASS      40.68 seconds
CheckSmatch                   PASS      110.56 seconds
BuildKernel32                 PASS      31.81 seconds
TestRunnerSetup               PASS      451.39 seconds
TestRunner_l2cap-tester       PASS      17.35 seconds
TestRunner_iso-tester         PASS      22.55 seconds
TestRunner_bnep-tester        PASS      5.84 seconds
TestRunner_mgmt-tester        PASS      117.28 seconds
TestRunner_rfcomm-tester      PASS      9.20 seconds
TestRunner_sco-tester         PASS      8.50 seconds
TestRunner_ioctl-tester       PASS      9.89 seconds
TestRunner_mesh-tester        PASS      7.29 seconds
TestRunner_smp-tester         PASS      8.38 seconds
TestRunner_userchan-tester    PASS      6.04 seconds
IncrementalBuild              PASS      30.04 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: L2CAP: don't check for out-of-bounds value

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
9: B1 Line exceeds max length (106>80): "  .../l2cap_core.c:4165 l2cap_connect() warn: impossible condition '(scid > 65535) => (0-u16max > u16max)'"


---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2023-05-26 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26 14:16 [PATCH] Bluetooth: L2CAP: don't check for out-of-bounds value Simon Horman
2023-05-26 14:34 ` Dan Carpenter
2023-05-26 15:19   ` Simon Horman
2023-05-30  6:33     ` Dan Carpenter
2023-05-26 14:57 ` 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=6470c8ce.0c0a0220.c4651.7003@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=horms@kernel.org \
    --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.