Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, cheng.jiang@oss.qualcomm.com
Subject: RE: Channel Sounding and RAP fixes
Date: Tue, 17 Nov 2026 04:15:53 -0800 (PST)	[thread overview]
Message-ID: <6afc4579.d49f74f3.340818.6a7b@mx.google.com> (raw)
In-Reply-To: <20261102081913.1623864-2-cheng.jiang@oss.qualcomm.com>

[-- Attachment #1: Type: text/plain, Size: 670 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:       Channel Sounding and RAP fixes
   Pull Request: https://github.com/bluez/bluez/pull/2747
   Created:      2026-11-02 08:24:26+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

  parent reply	other threads:[~2026-11-17 12:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02  8:18 [PATCH BlueZ 00/15] Channel Sounding and RAP fixes Cheng Jiang
2026-11-02  8:18 ` [PATCH BlueZ 01/15] gatt-database: Drop stale device state for removed bonds Cheng Jiang
2026-11-02  9:08   ` Channel Sounding and RAP fixes bluez.test.bot
2026-11-17 12:15   ` bluez.test.bot [this message]
2026-11-02  8:18 ` [PATCH BlueZ 02/15] shared/rap: Reset the readable Ranging Counters per connection Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 03/15] shared/rap: Subscribe on-demand data with the requested transport Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 04/15] shared/rap: Subscribe to Ranging Data when a measurement starts Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 05/15] client/cs: Fix use-after-free in stop_measurement_reply Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 06/15] shared/hci: Look up the connection handle on the right link Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 07/15] profiles/ranging: Let the Reflector run the CS setup phase Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 08/15] profiles/ranging: Let StartMeasurement() pick the Initiator for Both Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 09/15] profiles/ranging: Take the CS role from Config Complete Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 10/15] profiles/ranging: Act on a CS configuration created by the peer Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 11/15] profiles/ranging: Keep a peer-driven setup from being rewound Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 12/15] profiles/ranging: Defer CS Security Enable until the link is encrypted Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 13/15] profiles/ranging: Choose the CS antenna configuration from both ends Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 14/15] profiles/ranging: Do not start a procedure after StopMeasurement() Cheng Jiang
2026-11-02  8:19 ` [PATCH BlueZ 15/15] shared/rap: Start the Real-time timeout when the procedure starts Cheng Jiang
2026-11-03 20:38 ` [PATCH BlueZ 00/15] Channel Sounding and RAP fixes Luiz Augusto von Dentz
2026-11-04  3:04   ` Cheng Jiang
2026-11-04 15:07     ` Luiz Augusto von Dentz

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=6afc4579.d49f74f3.340818.6a7b@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=cheng.jiang@oss.qualcomm.com \
    --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