From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, derektern@proton.me
Subject: RE: [BlueZ,1/3] transport: Preserve Release on late BAP ready
Date: Sat, 03 Oct 2026 17:02:35 -0700 (PDT) [thread overview]
Message-ID: <6ac1979b.2d0a4cdb.13dd3d.ea0b@mx.google.com> (raw)
In-Reply-To: <5yh1Rc6x2sD0mB4Zq0o-3_jmYYKB43NbYyd-ZXGrHGZRN61HyoWYmLVVTTHE2-SyPhNj8g2ktGAB0Zy_Jnq-Htnc1JspqPSHvIsZDC3KFlM=@proton.me>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
This is an automated email and please do not reply to this email.
Dear Submitter,
This series was picked up by the CI more than 2 weeks ago and the pull
request created for it is still open, which means the series was never
applied to the tree.
Series: [BlueZ,1/3] transport: Preserve Release on late BAP ready
Pull Request: https://github.com/bluez/bluez/pull/2550
Created: 2026-09-18 22:25:01+00:00
The pull request has been closed and no further action is taken on this
series.
If the change should still be considered, it must be resent to the Linux
Bluetooth mailing list (linux-bluetooth@vger.kernel.org) so that it is
picked up again.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-04 0:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 20:21 [PATCH BlueZ 1/3] transport: Preserve Release on late BAP ready dt
2026-09-18 20:22 ` [PATCH BlueZ 2/3] bap: Recreate stream IO after an early Enable dt
2026-09-18 20:24 ` [PATCH BlueZ 3/3] test: Cover BAP transport release and reacquire dt
2026-09-18 21:44 ` Luiz Augusto von Dentz
2026-09-19 10:06 ` dt
2026-09-18 23:30 ` [BlueZ,1/3] transport: Preserve Release on late BAP ready bluez.test.bot
2026-10-04 0:02 ` bluez.test.bot [this message]
2026-10-07 18:40 ` [PATCH BlueZ 1/3] " 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=6ac1979b.2d0a4cdb.13dd3d.ea0b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=derektern@proton.me \
--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