From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v2] Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync
Date: Fri, 11 Aug 2023 11:20:07 -0700 (PDT) [thread overview]
Message-ID: <64d67bd7.050a0220.51e14.06bd@mx.google.com> (raw)
In-Reply-To: <20230811174633.1818931-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1427 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=775448
---Test result---
Test Summary:
CheckPatch PASS 0.77 seconds
GitLint PASS 0.33 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 44.80 seconds
CheckAllWarning PASS 48.41 seconds
CheckSparse PASS 54.47 seconds
CheckSmatch PASS 145.66 seconds
BuildKernel32 PASS 42.36 seconds
TestRunnerSetup PASS 639.62 seconds
TestRunner_l2cap-tester PASS 31.76 seconds
TestRunner_iso-tester PASS 72.96 seconds
TestRunner_bnep-tester PASS 14.73 seconds
TestRunner_mgmt-tester PASS 274.49 seconds
TestRunner_rfcomm-tester PASS 21.91 seconds
TestRunner_sco-tester PASS 24.41 seconds
TestRunner_ioctl-tester PASS 24.53 seconds
TestRunner_mesh-tester PASS 17.87 seconds
TestRunner_smp-tester PASS 19.13 seconds
TestRunner_userchan-tester PASS 15.05 seconds
IncrementalBuild PASS 39.65 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-08-11 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 17:46 [PATCH v2] Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync Luiz Augusto von Dentz
2023-08-11 18:20 ` bluez.test.bot [this message]
2023-08-11 23:04 ` Pauli Virtanen
2023-08-11 23:17 ` Luiz Augusto von Dentz
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=64d67bd7.050a0220.51e14.06bd@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.