From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: [v1,1/2] bluetooth: Remove codec id field in vendor codec definition
Date: Fri, 18 Nov 2022 19:56:16 -0800 (PST) [thread overview]
Message-ID: <637853e0.050a0220.a4bb3.ea57@mx.google.com> (raw)
In-Reply-To: <20221104071810.22720-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1486 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=691972
---Test result---
Test Summary:
CheckPatch PASS 1.47 seconds
GitLint PASS 0.68 seconds
SubjectPrefix FAIL 0.43 seconds
BuildKernel PASS 33.80 seconds
BuildKernel32 PASS 30.08 seconds
TestRunnerSetup PASS 417.72 seconds
TestRunner_l2cap-tester PASS 16.06 seconds
TestRunner_iso-tester PASS 15.93 seconds
TestRunner_bnep-tester PASS 5.50 seconds
TestRunner_mgmt-tester PASS 106.46 seconds
TestRunner_rfcomm-tester PASS 9.48 seconds
TestRunner_sco-tester PASS 8.78 seconds
TestRunner_ioctl-tester PASS 10.19 seconds
TestRunner_mesh-tester PASS 6.98 seconds
TestRunner_smp-tester PASS 8.82 seconds
TestRunner_userchan-tester PASS 5.81 seconds
IncrementalBuild PASS 37.51 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-19 3:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 7:18 [PATCH v1 1/2] bluetooth: Remove codec id field in vendor codec definition Kiran K
2022-11-04 7:18 ` [PATCH v1 2/2] bluetooth: Fix support for Read Local Supported Codecs V2 Kiran K
2022-11-04 8:03 ` [v1,1/2] bluetooth: Remove codec id field in vendor codec definition bluez.test.bot
2022-11-16 20:57 ` [PATCH v1 1/2] " Luiz Augusto von Dentz
2022-11-18 3:48 ` [v1,1/2] " bluez.test.bot
2022-11-18 4:34 ` bluez.test.bot
2022-11-18 5:30 ` bluez.test.bot
2022-11-18 6:34 ` bluez.test.bot
2022-11-18 7:33 ` bluez.test.bot
2022-11-18 8:36 ` bluez.test.bot
2022-11-18 9:31 ` bluez.test.bot
2022-11-19 3:56 ` bluez.test.bot [this message]
2022-11-19 5:02 ` bluez.test.bot
2022-12-01 20:00 ` [PATCH v1 1/2] " patchwork-bot+bluetooth
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=637853e0.050a0220.a4bb3.ea57@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 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.