From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: [v2,1/2] Bluetooth: Remove codec id field in vendor codec definition
Date: Tue, 15 Nov 2022 23:13:13 -0800 (PST) [thread overview]
Message-ID: <63748d89.050a0220.b0adc.c737@mx.google.com> (raw)
In-Reply-To: <20221116062918.11879-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1261 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=695805
---Test result---
Test Summary:
CheckPatch PASS 3.39 seconds
GitLint PASS 2.01 seconds
SubjectPrefix PASS 1.70 seconds
BuildKernel PASS 35.36 seconds
BuildKernel32 PASS 31.71 seconds
Incremental Build with patchesPASS 55.47 seconds
TestRunner: Setup PASS 528.98 seconds
TestRunner: l2cap-tester PASS 17.63 seconds
TestRunner: iso-tester PASS 17.38 seconds
TestRunner: bnep-tester PASS 6.74 seconds
TestRunner: mgmt-tester PASS 108.48 seconds
TestRunner: rfcomm-tester PASS 10.64 seconds
TestRunner: sco-tester PASS 10.09 seconds
TestRunner: ioctl-tester PASS 11.46 seconds
TestRunner: mesh-tester PASS 8.16 seconds
TestRunner: smp-tester PASS 10.10 seconds
TestRunner: userchan-tester PASS 7.03 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-16 7:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 6:29 [PATCH v2 1/2] Bluetooth: Remove codec id field in vendor codec definition Kiran K
2022-11-16 6:29 ` [PATCH v2 2/2] Bluetooth: Fix support for Read Local Supported Codecs V2 Kiran K
2022-11-16 7:13 ` bluez.test.bot [this message]
2022-11-18 4:15 ` [v2,1/2] Bluetooth: Remove codec id field in vendor codec definition bluez.test.bot
2022-11-18 5:07 ` bluez.test.bot
2022-11-18 5:52 ` 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=63748d89.050a0220.b0adc.c737@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kiran.k@intel.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