From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v3] Bluetooth: L2CAP: Fix leaking l2cap_conn objects
Date: Thu, 14 Sep 2023 15:02:30 -0700 (PDT) [thread overview]
Message-ID: <650382f6.050a0220.bf2af.3fc4@mx.google.com> (raw)
In-Reply-To: <20230914211133.3339473-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2263 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=784344
---Test result---
Test Summary:
CheckPatch FAIL 1.36 seconds
GitLint PASS 0.38 seconds
SubjectPrefix PASS 0.14 seconds
BuildKernel PASS 34.64 seconds
CheckAllWarning PASS 38.21 seconds
CheckSparse PASS 46.51 seconds
CheckSmatch PASS 117.13 seconds
BuildKernel32 PASS 33.76 seconds
TestRunnerSetup PASS 518.75 seconds
TestRunner_l2cap-tester PASS 30.61 seconds
TestRunner_iso-tester PASS 58.41 seconds
TestRunner_bnep-tester PASS 10.75 seconds
TestRunner_mgmt-tester PASS 226.15 seconds
TestRunner_rfcomm-tester PASS 16.41 seconds
TestRunner_sco-tester PASS 19.73 seconds
TestRunner_ioctl-tester PASS 18.39 seconds
TestRunner_mesh-tester PASS 13.67 seconds
TestRunner_smp-tester PASS 14.52 seconds
TestRunner_userchan-tester PASS 11.31 seconds
IncrementalBuild PASS 32.15 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v3] Bluetooth: L2CAP: Fix leaking l2cap_conn objects
WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#88:
Reported-by: Olivier L'Heureux <olivier.lheureux@fortrobotics.com>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
total: 0 errors, 1 warnings, 0 checks, 88 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/13386062.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.
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-09-14 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 21:11 [PATCH v3] Bluetooth: L2CAP: Fix leaking l2cap_conn objects Luiz Augusto von Dentz
2023-09-14 22:02 ` 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=650382f6.050a0220.bf2af.3fc4@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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 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.