All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [v2] Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled
Date: Sat, 13 Jun 2026 12:19:00 -0700 (PDT)	[thread overview]
Message-ID: <6a2dad24.d68db960.cf21b.9b0e@mx.google.com> (raw)
In-Reply-To: <9fdead8517c36f37c0b23b7b60f590d735792cfa.1781375875.git.pav@iki.fi>

[-- Attachment #1: Type: text/plain, Size: 988 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=1111109

---Test result---

Test Summary:
CheckPatch                    PASS      0.62 seconds
VerifyFixes                   PASS      0.09 seconds
VerifySignedoff               PASS      0.08 seconds
GitLint                       PASS      0.24 seconds
SubjectPrefix                 PASS      0.08 seconds
BuildKernel                   PASS      25.09 seconds
CheckAllWarning               PASS      27.75 seconds
CheckSparse                   PASS      26.42 seconds
BuildKernel32                 PASS      24.68 seconds
TestRunnerSetup               PASS      530.62 seconds
IncrementalBuild              PASS      23.82 seconds



https://github.com/bluez/bluetooth-next/pull/313

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-06-13 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-13 15:29 [PATCH] Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled Pauli Virtanen
2026-06-13 16:25 ` bluez.test.bot
2026-06-13 18:43 ` [PATCH v2] " Pauli Virtanen
2026-06-13 19:19   ` 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=6a2dad24.d68db960.cf21b.9b0e@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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.