From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, marcel@holtmann.org
Subject: RE: Bluetooth: Increment management interface revision
Date: Wed, 26 Jan 2022 10:01:18 -0800 (PST) [thread overview]
Message-ID: <61f18c6e.1c69fb81.5c7e0.5432@mx.google.com> (raw)
In-Reply-To: <20220126173012.81238-1-marcel@holtmann.org>
[-- 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=608717
---Test result---
Test Summary:
CheckPatch PASS 1.57 seconds
GitLint PASS 0.99 seconds
SubjectPrefix PASS 0.83 seconds
BuildKernel PASS 27.93 seconds
BuildKernel32 PASS 24.44 seconds
Incremental Build with patchesPASS 35.92 seconds
TestRunner: Setup PASS 422.60 seconds
TestRunner: l2cap-tester PASS 12.37 seconds
TestRunner: bnep-tester PASS 5.54 seconds
TestRunner: mgmt-tester PASS 96.92 seconds
TestRunner: rfcomm-tester PASS 6.75 seconds
TestRunner: sco-tester PASS 6.93 seconds
TestRunner: smp-tester PASS 6.92 seconds
TestRunner: userchan-tester PASS 5.78 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-01-26 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 17:30 [PATCH] Bluetooth: Increment management interface revision Marcel Holtmann
2022-01-26 18:01 ` bluez.test.bot [this message]
2022-01-27 20:36 ` Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 19:23 [PATCH] " Marcel Holtmann
2021-06-15 20:07 ` bluez.test.bot
2021-06-23 18:20 ` Luiz Augusto von Dentz
2020-12-07 10:02 [PATCH] " Marcel Holtmann
2020-12-07 11:08 ` 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=61f18c6e.1c69fb81.5c7e0.5432@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).