From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, soenke.huster@eknoes.de
Subject: RE: [RFC] Bluetooth: hci_event: Ignore multiple conn complete events
Date: Fri, 21 Jan 2022 10:04:59 -0800 (PST) [thread overview]
Message-ID: <61eaf5cb.1c69fb81.91822.932b@mx.google.com> (raw)
In-Reply-To: <20220121173622.192744-1-soenke.huster@eknoes.de>
[-- Attachment #1: Type: text/plain, Size: 1097 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=607341
---Test result---
Test Summary:
CheckPatch PASS 0.76 seconds
GitLint PASS 0.37 seconds
SubjectPrefix PASS 0.23 seconds
BuildKernel PASS 35.48 seconds
BuildKernel32 PASS 32.61 seconds
Incremental Build with patchesPASS 43.24 seconds
TestRunner: Setup PASS 547.21 seconds
TestRunner: l2cap-tester PASS 14.72 seconds
TestRunner: bnep-tester PASS 6.56 seconds
TestRunner: mgmt-tester PASS 118.55 seconds
TestRunner: rfcomm-tester PASS 8.44 seconds
TestRunner: sco-tester PASS 8.91 seconds
TestRunner: smp-tester PASS 8.40 seconds
TestRunner: userchan-tester PASS 7.11 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-01-21 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 17:36 [RFC PATCH] Bluetooth: hci_event: Ignore multiple conn complete events Soenke Huster
2022-01-21 18:04 ` bluez.test.bot [this message]
2022-01-21 18:22 ` Sönke Huster
2022-01-21 21:31 ` Luiz Augusto von Dentz
2022-01-21 23:18 ` Sönke Huster
2022-01-21 23:32 ` Luiz Augusto von Dentz
2022-01-21 23:52 ` Sönke Huster
2022-01-22 0:06 ` 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=61eaf5cb.1c69fb81.91822.932b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=soenke.huster@eknoes.de \
/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).