From: Paolo Abeni <pabeni@redhat.com>
To: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: anubhavg@qti.qualcomm.com, mohamull@qti.qualcomm.com,
hbandi@qti.qualcomm.com, Simon Horman <horms@kernel.org>,
linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: hci_sync: Add LE Channel Sounding HCI Command/event structures
Date: Fri, 19 Dec 2025 10:04:01 +0100 [thread overview]
Message-ID: <e1f053a7-791d-4433-b7ba-ea17a03ddfa7@redhat.com> (raw)
In-Reply-To: <20251217112523.2671279-1-naga.akella@oss.qualcomm.com>
On 12/17/25 12:25 PM, Naga Bhavani Akella wrote:
> 1. Implement LE Event Mask to include events required for
> LE Channel Sounding
> 2. Enable Channel Sounding feature bit in the
> LE Host Supported Features command
> 3. Define HCI command and event structures necessary for
> LE Channel Sounding functionality
>
> Signed-off-by: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
FYI, Jakub enabled automated AI review on the netdev CI, and the bot
found something suspicious in this patch, see:
https://netdev-ai.bots.linux.dev/ai-review.html?id=999e331e-1161-4eec-ad26-fafc3fea6cfd
I'm blindly forwarding the info, please have a look and evaluate it. Any
feedback in case of false positive would be useful!
Thanks,
Paolo
next prev parent reply other threads:[~2025-12-19 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 11:25 Naga Bhavani Akella
2025-12-19 9:04 ` Paolo Abeni [this message]
2025-12-19 14:27 ` 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=e1f053a7-791d-4433-b7ba-ea17a03ddfa7@redhat.com \
--to=pabeni@redhat.com \
--cc=anubhavg@qti.qualcomm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hbandi@qti.qualcomm.com \
--cc=horms@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mohamull@qti.qualcomm.com \
--cc=naga.akella@oss.qualcomm.com \
--cc=netdev@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
all inboxes | Powered by JetHome®