From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, jiangzp@google.com
Subject: RE: Bluetooth: hci_sync: hold hdev->lock when cleanup hci_conn
Date: Mon, 22 Aug 2022 22:25:22 -0700 (PDT) [thread overview]
Message-ID: <630464c2.050a0220.fc866.2fbb@mx.google.com> (raw)
In-Reply-To: <20220822214430.kernel.v2.1.I1d10fc551cadae988dcf2fc66ad8c9eec2d7026b@changeid>
[-- Attachment #1: Type: text/plain, Size: 1096 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=670006
---Test result---
Test Summary:
CheckPatch PASS 1.62 seconds
GitLint PASS 0.95 seconds
SubjectPrefix PASS 0.64 seconds
BuildKernel PASS 34.08 seconds
BuildKernel32 PASS 28.82 seconds
Incremental Build with patchesPASS 41.42 seconds
TestRunner: Setup PASS 479.01 seconds
TestRunner: l2cap-tester PASS 16.64 seconds
TestRunner: bnep-tester PASS 6.27 seconds
TestRunner: mgmt-tester PASS 99.95 seconds
TestRunner: rfcomm-tester PASS 9.53 seconds
TestRunner: sco-tester PASS 9.30 seconds
TestRunner: smp-tester PASS 9.30 seconds
TestRunner: userchan-tester PASS 6.39 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-08-23 5:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 4:44 [kernel PATCH v2 0/1] Bluetooth: hci_sync: hold hdev->lock when cleanup hci_conn Zhengping Jiang
2022-08-23 4:44 ` [kernel PATCH v2 1/1] " Zhengping Jiang
2022-08-23 5:25 ` bluez.test.bot [this message]
2022-08-23 11:06 ` Paolo Abeni
-- strict thread matches above, loose matches on Subject: below --
2022-08-23 17:28 [kernel PATCH v3 " Zhengping Jiang
2022-08-23 19:59 ` bluez.test.bot
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=630464c2.050a0220.fc866.2fbb@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=jiangzp@google.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.