From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, naga.akella@oss.qualcomm.com
Subject: RE: RAS: Add support for on-demand ranging data
Date: Mon, 07 Sep 2026 21:32:32 -0700 (PDT) [thread overview]
Message-ID: <6a9f8fe0.ac292227.3c9bee.339f@mx.google.com> (raw)
In-Reply-To: <20260908042727.1677501-2-naga.akella@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 382 bytes --]
This is an automated email and please do not reply to this email.
Dear Submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
While preparing the CI tests, the patches you submitted couldn't be applied to the current HEAD of the repository.
----- Output -----
Please resolve the issue and submit the patches again.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-08 4:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 4:27 [PATCH BlueZ v1 0/3] RAS: Add support for on-demand ranging data Naga Bhavani Akella
2026-09-08 4:27 ` [PATCH BlueZ v1 1/3] rap: Add OndemandRanging configuration option Naga Bhavani Akella
2026-09-08 4:32 ` bluez.test.bot [this message]
2026-09-08 18:29 ` RAS: Add support for on-demand ranging data bluez.test.bot
2026-09-08 4:27 ` [PATCH BlueZ v1 2/3] shared: add support for on-demand notification handling Naga Bhavani Akella
2026-09-08 4:27 ` [PATCH BlueZ v1 3/3] profiles: honor OndemandRanging config for RAS Initiator Naga Bhavani Akella
2026-09-08 19:20 ` [PATCH BlueZ v1 0/3] RAS: Add support for on-demand ranging data patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2026-09-07 13:56 [PATCH BlueZ v1 1/3] rap: Add OndemandRanging configuration option Naga Bhavani Akella
2026-09-07 15:49 ` RAS: Add support for on-demand ranging data 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=6a9f8fe0.ac292227.3c9bee.339f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=naga.akella@oss.qualcomm.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