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, 04 Nov 2022 01:03:26 -0700 (PDT) [thread overview]
Message-ID: <6364c74e.050a0220.d1c17.5bcd@mx.google.com> (raw)
In-Reply-To: <20221104071810.22720-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1475 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 2.77 seconds
GitLint PASS 1.56 seconds
SubjectPrefix FAIL 1.47 seconds
BuildKernel PASS 34.13 seconds
BuildKernel32 PASS 30.32 seconds
Incremental Build with patchesPASS 50.73 seconds
TestRunner: Setup PASS 504.89 seconds
TestRunner: l2cap-tester PASS 16.86 seconds
TestRunner: iso-tester PASS 16.30 seconds
TestRunner: bnep-tester PASS 6.27 seconds
TestRunner: mgmt-tester PASS 102.15 seconds
TestRunner: rfcomm-tester PASS 10.00 seconds
TestRunner: sco-tester PASS 9.37 seconds
TestRunner: ioctl-tester PASS 10.59 seconds
TestRunner: mesh-tester PASS 7.63 seconds
TestRunner: smp-tester PASS 9.48 seconds
TestRunner: userchan-tester PASS 6.41 seconds
Details
##############################
Test: SubjectPrefix - FAIL - 1.47 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-04 8:03 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 ` bluez.test.bot [this message]
2022-11-16 20:57 ` [PATCH v1 1/2] bluetooth: Remove codec id field in vendor codec definition 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
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=6364c74e.050a0220.d1c17.5bcd@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