From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, jingxiangfeng@huawei.com
Subject: RE: Bluetooth: btmtksdio: Add the missed release_firmware() in mtk_setup_firmware()
Date: Mon, 16 Nov 2020 19:17:00 -0800 (PST) [thread overview]
Message-ID: <5fb340ac.1c69fb81.7cd1f.7b10@mx.google.com> (raw)
In-Reply-To: <20201117024332.165771-1-jingxiangfeng@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1258 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=385607
---Test result---
##############################
Test: CheckPatch - FAIL
Output:
workflow: Add workflow files for ci
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#20:
new file mode 100644
total: 0 errors, 1 warnings, 49 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
"[PATCH] workflow: Add workflow files for ci" has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: CheckGitLint - FAIL
Output:
Bluetooth: btmtksdio: Add the missed release_firmware() in mtk_setup_firmware()
1: T1 Title exceeds max length (79>72): "Bluetooth: btmtksdio: Add the missed release_firmware() in mtk_setup_firmware()"
##############################
Test: CheckBuildK - PASS
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2020-11-17 3:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 2:43 [PATCH] Bluetooth: btmtksdio: Add the missed release_firmware() in mtk_setup_firmware() Jing Xiangfeng
2020-11-17 2:43 ` Jing Xiangfeng
2020-11-17 2:43 ` Jing Xiangfeng
2020-11-17 3:17 ` bluez.test.bot [this message]
2020-11-23 11:51 ` Marcel Holtmann
2020-11-23 11:51 ` Marcel Holtmann
2020-11-23 11:51 ` 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=5fb340ac.1c69fb81.7cd1f.7b10@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=jingxiangfeng@huawei.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.