From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, colin.king@canonical.com
Subject: RE: [next] Bluetooth: virtio_bt: add missing null pointer check on alloc_skb call return
Date: Fri, 09 Apr 2021 10:32:07 -0700 (PDT) [thread overview]
Message-ID: <60708f97.1c69fb81.90303.86ff@mx.google.com> (raw)
In-Reply-To: <20210409165314.671165-1-colin.king@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 2812 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=464573
---Test result---
##############################
Test: CheckPatch - FAIL
Bluetooth: virtio_bt: add missing null pointer check on alloc_skb call return
WARNING: Unknown commit id 'afd2daa26c7a', maybe rebased or not pulled?
#11:
Fixes: afd2daa26c7a ("Bluetooth: Add support for virtio transport driver")
total: 0 errors, 1 warnings, 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.
"[PATCH] Bluetooth: virtio_bt: add missing null pointer check on" has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: CheckGitLint - FAIL
Bluetooth: virtio_bt: add missing null pointer check on alloc_skb call return
1: T1 Title exceeds max length (77>72): "Bluetooth: virtio_bt: add missing null pointer check on alloc_skb call return"
##############################
Test: CheckBuildK - PASS
##############################
Test: CheckTestRunner: Setup - PASS
##############################
Test: CheckTestRunner: l2cap-tester - PASS
Total: 40, Passed: 34 (85.0%), Failed: 0, Not Run: 6
##############################
Test: CheckTestRunner: bnep-tester - PASS
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0
##############################
Test: CheckTestRunner: mgmt-tester - FAIL
Total: 416, Passed: 396 (95.2%), Failed: 6, Not Run: 14
Failed Test Cases
Set connectable off (LE) - Success 2 Failed 0.020 seconds
Set connectable off (LE) - Success 3 Failed 0.024 seconds
Set connectable off (LE) - Success 4 Failed 0.024 seconds
Add Advertising - Success 13 (ADV_SCAN_IND) Failed 0.024 seconds
Add Advertising - Success 14 (ADV_NONCONN_IND) Failed 0.020 seconds
Add Advertising - Success 17 (Connectable -> off) Failed 0.020 seconds
##############################
Test: CheckTestRunner: rfcomm-tester - PASS
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0
##############################
Test: CheckTestRunner: sco-tester - PASS
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: CheckTestRunner: smp-tester - PASS
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: CheckTestRunner: userchan-tester - PASS
Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0
---
Regards,
Linux Bluetooth
[-- Attachment #2: l2cap-tester.log --]
[-- Type: application/octet-stream, Size: 43344 bytes --]
[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3536 bytes --]
[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 547571 bytes --]
[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 11656 bytes --]
[-- Attachment #6: sco-tester.log --]
[-- Type: application/octet-stream, Size: 9891 bytes --]
[-- Attachment #7: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11802 bytes --]
[-- Attachment #8: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 5432 bytes --]
next prev parent reply other threads:[~2021-04-09 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 16:53 [PATCH][next] Bluetooth: virtio_bt: add missing null pointer check on alloc_skb call return Colin King
2021-04-09 17:32 ` bluez.test.bot [this message]
2021-04-11 11:56 ` Marcel Holtmann
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=60708f97.1c69fb81.90303.86ff@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=colin.king@canonical.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.