All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, eadavis@qq.com
Subject: RE: [v2] Bluetooth: Ignore too large handle values in BIG
Date: Mon, 17 Jun 2024 04:57:38 -0700 (PDT)	[thread overview]
Message-ID: <667024b2.050a0220.b69f7.de01@mx.google.com> (raw)
In-Reply-To: <tencent_E43E1B2F25E4BA5EBBEC33229E5E1BEB4B08@qq.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      2.06 seconds
GitLint                       PASS      4.56 seconds
SubjectPrefix                 PASS      0.62 seconds
BuildKernel                   PASS      29.96 seconds
CheckAllWarning               PASS      32.46 seconds
CheckSparse                   WARNING   40.13 seconds
CheckSmatch                   WARNING   102.67 seconds
BuildKernel32                 PASS      28.72 seconds
TestRunnerSetup               PASS      524.19 seconds
TestRunner_l2cap-tester       PASS      18.30 seconds
TestRunner_iso-tester         PASS      35.14 seconds
TestRunner_bnep-tester        PASS      5.30 seconds
TestRunner_mgmt-tester        PASS      111.24 seconds
TestRunner_rfcomm-tester      PASS      7.65 seconds
TestRunner_sco-tester         PASS      12.97 seconds
TestRunner_ioctl-tester       PASS      7.84 seconds
TestRunner_mesh-tester        PASS      5.98 seconds
TestRunner_smp-tester         PASS      6.88 seconds
TestRunner_userchan-tester    PASS      5.01 seconds
IncrementalBuild              PASS      28.44 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2] Bluetooth: Ignore too large handle values in BIG
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#91: 
handle value is belonging to ida id range, otherwise ida will be erroneously

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

/github/workspace/src/src/13700520.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: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):


---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-06-17 11:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28  4:53 [syzbot] [bluetooth?] WARNING in hci_conn_del syzbot
2024-06-13 21:15 ` [syzbot] " syzbot
2024-06-16 10:14 ` [syzbot] [bluetooth?] " Edward Adam Davis
2024-06-16 10:33   ` syzbot
2024-06-16 10:20 ` [PATCH] bluetooth: handle value within the ida range should not be handled in BIG Edward Adam Davis
2024-06-16 10:37   ` Pavel Skripkin
2024-06-16 13:18     ` [syzbot] [bluetooth?] WARNING in hci_conn_del Edward Adam Davis
2024-06-16 10:59   ` bluetooth: handle value within the ida range should not be handled in BIG bluez.test.bot
2024-06-16 13:21     ` [PATCH] Bluetooth: handle value is too large should not be used " Edward Adam Davis
2024-06-16 14:33       ` bluez.test.bot
2024-06-16 20:44       ` [PATCH] " Paul Menzel
2024-06-17 11:09         ` [PATCH v2] Bluetooth: Ignore too large handle values " Edward Adam Davis
2024-06-17 11:57           ` bluez.test.bot [this message]
2024-06-17 14:10           ` patchwork-bot+bluetooth

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=667024b2.050a0220.b69f7.de01@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=eadavis@qq.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 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.