From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dinghao.liu@zju.edu.cn
Subject: RE: Bluetooth: btmtkuart: fix a memleak in mtk_hci_wmt_sync
Date: Wed, 22 Sep 2021 08:02:53 -0700 (PDT) [thread overview]
Message-ID: <614b459d.1c69fb81.456b3.7a67@mx.google.com> (raw)
In-Reply-To: <20210922134945.27503-1-dinghao.liu@zju.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 1292 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=551035
---Test result---
Test Summary:
CheckPatch PASS 0.87 seconds
GitLint FAIL 0.30 seconds
BuildKernel PASS 667.69 seconds
TestRunner: Setup PASS 434.04 seconds
TestRunner: l2cap-tester PASS 3.30 seconds
TestRunner: bnep-tester PASS 2.21 seconds
TestRunner: mgmt-tester PASS 35.74 seconds
TestRunner: rfcomm-tester PASS 2.57 seconds
TestRunner: smp-tester PASS 2.60 seconds
TestRunner: userchan-tester PASS 2.28 seconds
Details
##############################
Test: GitLint - FAIL - 0.30 seconds
Run gitlint with rule in .gitlint
Bluetooth: btmtkuart: fix a memleak in mtk_hci_wmt_sync
2: B4 Second line is not empty: "of mtk_hci_wmt_sync, while the other error paths do not free it,"
6: B1 Line exceeds max length (101>80): "Fixes: e0b67035a90b ("Bluetooth: mediatek: update the common setup between MT7622 and other devices")"
---
Regards,
Linux Bluetooth
[-- Attachment #2: l2cap-tester.log --]
[-- Type: application/octet-stream, Size: 51566 bytes --]
[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3934 bytes --]
[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 626747 bytes --]
[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 14791 bytes --]
[-- Attachment #6: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11857 bytes --]
[-- Attachment #7: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 7768 bytes --]
prev parent reply other threads:[~2021-09-22 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 13:49 [PATCH] Bluetooth: btmtkuart: fix a memleak in mtk_hci_wmt_sync Dinghao Liu
2021-09-22 13:49 ` Dinghao Liu
2021-09-22 13:49 ` Dinghao Liu
2021-09-22 14:16 ` Marcel Holtmann
2021-09-22 14:16 ` Marcel Holtmann
2021-09-22 14:16 ` Marcel Holtmann
2021-09-22 15:02 ` bluez.test.bot [this message]
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=614b459d.1c69fb81.456b3.7a67@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=dinghao.liu@zju.edu.cn \
--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.