From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, proxy-alt@proxy-alt.dev
Subject: RE: [BlueZ,v3,1/2] shared/gatt-client: verify a synthesized CCC before writing
Date: Sat, 19 Sep 2026 17:42:44 -0700 (PDT) [thread overview]
Message-ID: <6aaf2c04.c9c553e2.155e46.354c@mx.google.com> (raw)
In-Reply-To: <20260904213642.68792-1-proxy-alt@proxy-alt.dev>
[-- Attachment #1: Type: text/plain, Size: 714 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,v3,1/2] shared/gatt-client: verify a synthesized CCC before writing
Pull Request: https://github.com/bluez/bluez/pull/2495
Created: 2026-09-04 23:15:00+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-09-20 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 18:28 [PATCH BlueZ v2] shared/gatt-client: confirm a synthesized CCC handle before writing to it Proxy alt
2026-09-04 20:13 ` [BlueZ,v2] " bluez.test.bot
2026-09-04 21:36 ` [PATCH BlueZ v3 1/2] shared/gatt-client: verify a synthesized CCC before writing Proxy alt
2026-09-04 21:36 ` [PATCH BlueZ v3 2/2] unit/test-micp: expect the FIND_INFORMATION the CCC fix adds Proxy alt
2026-09-04 23:47 ` [BlueZ,v3,1/2] shared/gatt-client: verify a synthesized CCC before writing bluez.test.bot
2026-09-20 0:42 ` bluez.test.bot [this message]
2026-09-19 21:05 ` [BlueZ,v2] shared/gatt-client: confirm a synthesized CCC handle before writing to it 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=6aaf2c04.c9c553e2.155e46.354c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=proxy-alt@proxy-alt.dev \
/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