From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dan.carpenter@oracle.com
Subject: RE: [1/2] Bluetooth: ISO: unlock on error path in iso_sock_setsockopt()
Date: Wed, 27 Jul 2022 06:37:35 -0700 (PDT) [thread overview]
Message-ID: <62e13f9f.1c69fb81.fd496.8c42@mx.google.com> (raw)
In-Reply-To: <YuEq2Aey0VOrxPB+@kili>
[-- Attachment #1: Type: text/plain, Size: 1098 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=663427
---Test result---
Test Summary:
CheckPatch PASS 3.49 seconds
GitLint PASS 1.67 seconds
SubjectPrefix PASS 1.21 seconds
BuildKernel PASS 35.53 seconds
BuildKernel32 PASS 31.02 seconds
Incremental Build with patchesPASS 48.90 seconds
TestRunner: Setup PASS 509.47 seconds
TestRunner: l2cap-tester PASS 17.95 seconds
TestRunner: bnep-tester PASS 6.84 seconds
TestRunner: mgmt-tester PASS 106.23 seconds
TestRunner: rfcomm-tester PASS 10.13 seconds
TestRunner: sco-tester PASS 9.97 seconds
TestRunner: smp-tester PASS 9.88 seconds
TestRunner: userchan-tester PASS 6.87 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-07-27 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 12:08 [PATCH 1/2] Bluetooth: ISO: unlock on error path in iso_sock_setsockopt() Dan Carpenter
2022-07-27 12:10 ` [PATCH 2/2] Bluetooth: ISO: fix info leak in iso_sock_getsockopt() Dan Carpenter
2022-07-27 19:51 ` Luiz Augusto von Dentz
2022-07-28 6:40 ` Dan Carpenter
2022-07-27 13:37 ` bluez.test.bot [this message]
2022-07-27 20:00 ` [PATCH 1/2] Bluetooth: ISO: unlock on error path in iso_sock_setsockopt() 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=62e13f9f.1c69fb81.fd496.8c42@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=dan.carpenter@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox