From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, josephsih@chromium.org
Subject: RE: [v1,1/2] Bluetooth: aosp: surface AOSP quality report through mgmt
Date: Fri, 21 Jan 2022 03:57:01 -0800 (PST) [thread overview]
Message-ID: <61ea9f8d.1c69fb81.6e5ca.22df@mx.google.com> (raw)
In-Reply-To: <20220121192152.v1.1.I2015b42d2d0a502334c9c3a2983438b89716d4f0@changeid>
[-- 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=607231
---Test result---
Test Summary:
CheckPatch PASS 4.77 seconds
GitLint PASS 1.99 seconds
SubjectPrefix PASS 1.69 seconds
BuildKernel PASS 36.40 seconds
BuildKernel32 PASS 32.88 seconds
Incremental Build with patchesPASS 74.26 seconds
TestRunner: Setup PASS 564.84 seconds
TestRunner: l2cap-tester PASS 15.78 seconds
TestRunner: bnep-tester PASS 7.40 seconds
TestRunner: mgmt-tester PASS 126.11 seconds
TestRunner: rfcomm-tester PASS 9.67 seconds
TestRunner: sco-tester PASS 10.10 seconds
TestRunner: smp-tester PASS 9.89 seconds
TestRunner: userchan-tester PASS 8.40 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-01-21 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 11:22 [PATCH v1 1/2] Bluetooth: aosp: surface AOSP quality report through mgmt Joseph Hwang
2022-01-21 11:22 ` [PATCH v1 2/2] Bluetooth: btintel: surface Intel telemetry events " Joseph Hwang
2022-01-21 18:30 ` kernel test robot
2022-01-21 18:30 ` kernel test robot
2022-01-21 20:21 ` Marcel Holtmann
2022-01-22 7:31 ` kernel test robot
2022-01-22 7:31 ` kernel test robot
2022-01-21 11:57 ` bluez.test.bot [this message]
2022-01-21 20:16 ` [PATCH v1 1/2] Bluetooth: aosp: surface AOSP quality report " Marcel Holtmann
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=61ea9f8d.1c69fb81.6e5ca.22df@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=josephsih@chromium.org \
--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.