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] avdtp: Fix error parsing from failed delay report request
Date: Sun, 22 Nov 2026 10:39:36 -0800 (PST)	[thread overview]
Message-ID: <6b0336e8.9ebd51ef.1441fc.3da0@mx.google.com> (raw)
In-Reply-To: <20261122103851.681782-1-simon.mikuda@streamunlimited.com>

[-- Attachment #1: Type: text/plain, Size: 1020 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/series/1218571/

---Test result---

Test Summary:
CheckPatch                    PASS      0.47 seconds
GitLint                       PASS      0.32 seconds
BuildEll                      PASS      16.23 seconds
BluezMake                     PASS      236.38 seconds
MakeCheck                     PASS      2.66 seconds
MakeDistcheck                 PASS      119.52 seconds
CheckValgrind                 PASS      122.69 seconds
CheckSmatch                   PASS      240.77 seconds
bluezmakeextell               PASS      79.79 seconds
TestFunctional                PASS      1047.08 seconds
IncrementalBuild              PASS      242.21 seconds
ScanBuild                     PASS      876.72 seconds



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

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-11-22 18:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-22 10:38 [PATCH BlueZ] avdtp: Fix error parsing from failed delay report request Simon Mikuda
2026-11-22 18:39 ` 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=6b0336e8.9ebd51ef.1441fc.3da0@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