From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, naga.akella@oss.qualcomm.com
Subject: RE: Bluetooth: Add initial Channel Sounding
Date: Thu, 02 Apr 2026 03:49:01 -0700 (PDT) [thread overview]
Message-ID: <69ce499d.050a0220.b2460.0f8d@mx.google.com> (raw)
In-Reply-To: <20260402103900.310778-2-naga.akella@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 544 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 -----
error: src/shared/rap.c: does not exist in index
error: src/shared/rap.h: does not exist in index
hint: Use 'git am --show-current-patch' to see the failed patch
Please resolve the issue and submit the patches again.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-04-02 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 10:38 [PATCH BlueZ v1 0/3] Bluetooth: Add initial Channel Sounding Naga Bhavani Akella
2026-04-02 10:38 ` [PATCH BlueZ v1 1/3] shared: rap: Introduce Channel Sounding HCI raw interface support Naga Bhavani Akella
2026-04-02 10:49 ` bluez.test.bot [this message]
2026-04-02 15:28 ` Luiz Augusto von Dentz
2026-04-02 15:56 ` Naga Bhavani Akella
2026-04-02 10:38 ` [PATCH BlueZ v1 2/3] bluetooth: Add Channel Sounding config parsing support Naga Bhavani Akella
2026-04-02 15:33 ` Luiz Augusto von Dentz
2026-04-02 10:39 ` [PATCH BlueZ v1 3/3] profiles: ranging: Add HCI LE Event Handling in Reflector role Naga Bhavani Akella
2026-04-02 15:58 ` Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2026-04-07 10:35 [PATCH BlueZ v2 1/3] shared: rap: Introduce Channel Sounding HCI raw interface support Naga Bhavani Akella
2026-04-07 11:31 ` Bluetooth: Add initial Channel Sounding 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=69ce499d.050a0220.b2460.0f8d@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