From: Chris Down <chris@chrisdown.name>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com,
Jaganath Kanakkassery <jaganath.k.os@gmail.com>
Subject: Re: [PATCH] Bluetooth: hci_event: Mask data status from LE ext adv reports
Date: Sun, 20 Jul 2025 00:04:19 +0800 [thread overview]
Message-ID: <aHvCA4YFoQPbFChv@chrisdown.name> (raw)
In-Reply-To: <CABBYNZJ60JUyz30u8QXvv6OO5dAu1A5-JDB_jJ=H_yR6+WYfng@mail.gmail.com>
Hi Luiz,
>Try to capture one of them using btmon and then add to the patch description.
Thanks, I have one now and will add for v2.
>> >> - if (evt_type == LE_EXT_ADV_NON_CONN_IND ||
>> >> - evt_type & LE_EXT_ADV_DIRECT_IND)
>> >> + if (pdu_type == LE_EXT_ADV_NON_CONN_IND ||
>> >
>> >I'm not sure I would keep checking for LE_EXT_ADV_NON_CONN_IND, maybe
>> >just return LE_ADV_NONCONN_IND, LE_EXT_ADV_NON_CONN_IND is not
>> >actually a bit it is the absence of any bits being set, so I guess the
>> >only invalid adv are the ones for legacy which seem to require a bit
>> >to be set.
>>
>> So are you thinking of doing this?
>>
>> if (!(pdu_type & ~(LE_EXT_ADV_DIRECT_IND)))
>> return LE_ADV_NONCONN_IND;
>
>We can probably return early on if (!evt_type) return
>LE_ADV_NONCONN_IND since there is no point in evaluating it if it is
>zero.
I guess you meant `if (!pdu_type)`? That correctly handles the 0x40 case (where
pdu_type becomes 0), but it would miss non-connectable directed advertisements
(PDU type 0x04), right? Or maybe you meant something else?
next prev parent reply other threads:[~2025-07-19 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 17:14 [PATCH] Bluetooth: hci_event: Mask data status from LE ext adv reports Chris Down
2025-07-16 17:36 ` bluez.test.bot
2025-07-17 19:12 ` [PATCH] " Luiz Augusto von Dentz
2025-07-18 8:13 ` Chris Down
2025-07-18 16:05 ` Luiz Augusto von Dentz
2025-07-19 16:04 ` Chris Down [this message]
2025-07-21 13:34 ` 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=aHvCA4YFoQPbFChv@chrisdown.name \
--to=chris@chrisdown.name \
--cc=jaganath.k.os@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.