From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yin31149@gmail.com
Subject: RE: Bluetooth: L2CAP: Fix memory leak in vhci_write
Date: Mon, 17 Oct 2022 01:37:21 -0700 (PDT) [thread overview]
Message-ID: <634d1441.a70a0220.201d3.b4c9@mx.google.com> (raw)
In-Reply-To: <20221017074432.12177-1-yin31149@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2360 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=685727
---Test result---
Test Summary:
CheckPatch FAIL 0.99 seconds
GitLint FAIL 0.49 seconds
SubjectPrefix PASS 0.31 seconds
BuildKernel PASS 44.65 seconds
BuildKernel32 PASS 40.74 seconds
Incremental Build with patchesPASS 58.75 seconds
TestRunner: Setup PASS 661.99 seconds
TestRunner: l2cap-tester PASS 21.06 seconds
TestRunner: iso-tester PASS 21.23 seconds
TestRunner: bnep-tester PASS 8.15 seconds
TestRunner: mgmt-tester PASS 133.51 seconds
TestRunner: rfcomm-tester PASS 12.73 seconds
TestRunner: sco-tester PASS 11.87 seconds
TestRunner: ioctl-tester PASS 13.82 seconds
TestRunner: mesh-tester PASS 10.06 seconds
TestRunner: smp-tester PASS 11.82 seconds
TestRunner: userchan-tester PASS 8.53 seconds
Details
##############################
Test: CheckPatch - FAIL - 0.99 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: L2CAP: Fix memory leak in vhci_write\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#124:
Reported-and-tested-by: syzbot+8f819e36e01022991cfa@syzkaller.appspotmail.com
total: 0 errors, 1 warnings, 0 checks, 19 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/13008275.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 - 0.49 seconds
Run gitlint with rule in .gitlint
Bluetooth: L2CAP: Fix memory leak in vhci_write
14: B1 Line exceeds max length (84>80): " [<ffffffff833f742f>] bt_skb_alloc include/net/bluetooth/bluetooth.h:469 [inline]"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-10-17 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 7:44 [PATCH] Bluetooth: L2CAP: Fix memory leak in vhci_write Hawkins Jiawei
2022-10-17 8:37 ` bluez.test.bot [this message]
2022-10-17 20:01 ` Luiz Augusto von Dentz
2022-10-18 1:16 ` Hawkins Jiawei
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=634d1441.a70a0220.201d3.b4c9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yin31149@gmail.com \
/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