Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, simon.mikuda@streamunlimited.com
Subject: RE: [BlueZ] avrcp: Abort continuing response on fragmented CT replies
Date: Tue, 09 Jun 2026 16:06:30 -0700 (PDT)	[thread overview]
Message-ID: <6a289c76.04ac118e.a66e0.5f53@mx.google.com> (raw)
In-Reply-To: <20260609212656.3900190-1-simon.mikuda@streamunlimited.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.47 seconds
GitLint                       PASS      0.32 seconds
BuildEll                      PASS      20.54 seconds
BluezMake                     PASS      650.26 seconds
MakeCheck                     PASS      3.37 seconds
MakeDistcheck                 PASS      248.95 seconds
CheckValgrind                 PASS      225.60 seconds
CheckSmatch                   PASS      353.04 seconds
bluezmakeextell               PASS      182.32 seconds
IncrementalBuild              PASS      659.64 seconds
ScanBuild                     PASS      1039.95 seconds



https://github.com/bluez/bluez/pull/2211

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-06-09 23:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 21:26 [PATCH BlueZ] avrcp: Abort continuing response on fragmented CT replies Simon Mikuda
2026-06-09 23:06 ` bluez.test.bot [this message]
2026-06-10 18:40 ` 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=6a289c76.04ac118e.a66e0.5f53@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=simon.mikuda@streamunlimited.com \
    /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