From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: linux-bluetooth@vger.kernel.org
Cc: senozhatsky@chromium.org
Subject: Re: Bluetooth: btmtksdio: teardown fixes
Date: Thu, 18 Jun 2026 12:09:48 +0900 [thread overview]
Message-ID: <ajNhPdupuPzVEt9F@google.com> (raw)
In-Reply-To: <6a324a47.14d9b9dc.267f5a.d138@mx.google.com>
On (26/06/17 00:18), bluez.test.bot@gmail.com wrote:
> 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=1112708
>
[..]
> ##############################
> Test: GitLint - FAIL
> Desc: Run gitlint
> Output:
> [v3,2/2] Bluetooth: btmtksdio: call cancel_work_sync() outside of host lock scope
>
> 1: T1 Title exceeds max length (81>80): "[v3,2/2] Bluetooth: btmtksdio: call cancel_work_sync() outside of host lock scope"
> 6: B3 Line contains hard tab characters (\t): "CPU0 CPU1"
> 7: B3 Line contains hard tab characters (\t): " close()/reset()"
> 8: B3 Line contains hard tab characters (\t): " sdio_claim_host()"
> 11: B3 Line contains hard tab characters (\t): " cancel_work_sync() // sleeps"
> ##############################
Are these critical errors? Should I re-submit?
next prev parent reply other threads:[~2026-06-18 3:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 6:45 [PATCH v3 0/2] Bluetooth: btmtksdio: teardown fixes Sergey Senozhatsky
2026-06-17 6:45 ` [PATCH v3 1/2] Bluetooth: btmtksdio: test for BUS IO errors in btmtksdio_txrx_work() Sergey Senozhatsky
2026-06-17 7:18 ` Bluetooth: btmtksdio: teardown fixes bluez.test.bot
2026-06-18 3:09 ` Sergey Senozhatsky [this message]
2026-06-17 6:45 ` [PATCH v3 2/2] Bluetooth: btmtksdio: call cancel_work_sync() outside of host lock scope Sergey Senozhatsky
-- strict thread matches above, loose matches on Subject: below --
2026-06-18 3:13 [PATCH v4 1/2] Bluetooth: btmtksdio: test for BUS IO errors in btmtksdio_txrx_work() Sergey Senozhatsky
2026-06-18 5:41 ` Bluetooth: btmtksdio: teardown fixes bluez.test.bot
2026-06-16 11:12 [PATCH v2 1/3] Bluetooth: btmtksdio: correct btmtksdio_txrx_work() loop timeout check Sergey Senozhatsky
2026-06-16 15:30 ` Bluetooth: btmtksdio: teardown fixes 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=ajNhPdupuPzVEt9F@google.com \
--to=senozhatsky@chromium.org \
--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