From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yinghsu@chromium.org
Subject: RE: [v3] Bluetooth: Fix possible deadlock in rfcomm_sk_state_change
Date: Tue, 10 Jan 2023 19:57:10 -0800 (PST) [thread overview]
Message-ID: <63be3396.170a0220.797a1.de6d@mx.google.com> (raw)
In-Reply-To: <20230111031540.v3.1.I1f29bb547a03e9adfe2e6754212f9d14a2e39c4b@changeid>
[-- Attachment #1: Type: text/plain, Size: 1997 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=710770
---Test result---
Test Summary:
CheckPatch PASS 0.77 seconds
GitLint FAIL 0.53 seconds
SubjectPrefix PASS 0.05 seconds
BuildKernel PASS 30.88 seconds
CheckAllWarning PASS 33.71 seconds
CheckSparse PASS 38.46 seconds
CheckSmatch PASS 106.19 seconds
BuildKernel32 PASS 29.67 seconds
TestRunnerSetup PASS 427.02 seconds
TestRunner_l2cap-tester PASS 15.97 seconds
TestRunner_iso-tester PASS 16.16 seconds
TestRunner_bnep-tester PASS 5.52 seconds
TestRunner_mgmt-tester PASS 105.33 seconds
TestRunner_rfcomm-tester PASS 8.60 seconds
TestRunner_sco-tester PASS 7.89 seconds
TestRunner_ioctl-tester PASS 9.18 seconds
TestRunner_mesh-tester PASS 6.85 seconds
TestRunner_smp-tester PASS 7.81 seconds
TestRunner_userchan-tester PASS 5.69 seconds
IncrementalBuild PASS 27.91 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v3] Bluetooth: Fix possible deadlock in rfcomm_sk_state_change
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
19: B3 Line contains hard tab characters (\t): " lock_sock(sk)"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-01-11 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 3:16 [PATCH v3] Bluetooth: Fix possible deadlock in rfcomm_sk_state_change Ying Hsu
2023-01-11 3:57 ` bluez.test.bot [this message]
2023-01-11 20: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=63be3396.170a0220.797a1.de6d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yinghsu@chromium.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.