From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: Bluetooth: RFCOMM: Fix possible deadlock on socket shutdown/release
Date: Tue, 13 Sep 2022 17:13:12 -0700 (PDT) [thread overview]
Message-ID: <63211c98.a70a0220.fc7d7.e5ba@mx.google.com> (raw)
In-Reply-To: <20220913233157.526041-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1478 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=676714
---Test result---
Test Summary:
CheckPatch PASS 0.92 seconds
GitLint FAIL 0.47 seconds
SubjectPrefix PASS 0.31 seconds
BuildKernel PASS 45.45 seconds
BuildKernel32 PASS 40.12 seconds
Incremental Build with patchesPASS 59.47 seconds
TestRunner: Setup PASS 667.48 seconds
TestRunner: l2cap-tester PASS 20.48 seconds
TestRunner: iso-tester PASS 20.45 seconds
TestRunner: bnep-tester PASS 7.74 seconds
TestRunner: mgmt-tester PASS 127.19 seconds
TestRunner: rfcomm-tester PASS 12.53 seconds
TestRunner: sco-tester PASS 11.90 seconds
TestRunner: smp-tester PASS 11.79 seconds
TestRunner: userchan-tester PASS 8.35 seconds
Details
##############################
Test: GitLint - FAIL - 0.47 seconds
Run gitlint with rule in .gitlint
Bluetooth: RFCOMM: Fix possible deadlock on socket shutdown/release
21: B1 Line exceeds max length (101>80): "Link: https://lore.kernel.org/all/CAD+dNTsbuU4w+Y_P7o+VEN7BYCAbZuwZx2+tH+OTzCdcZF82YA@mail.gmail.com/"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-09-14 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 23:31 [PATCH] Bluetooth: RFCOMM: Fix possible deadlock on socket shutdown/release Luiz Augusto von Dentz
2022-09-14 0:13 ` bluez.test.bot [this message]
2022-09-14 18:57 ` Luiz Augusto von Dentz
2022-09-15 21:10 ` [PATCH] " 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=63211c98.a70a0220.fc7d7.e5ba@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).