From: Yang Li <yang.li@amlogic.com>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_sync: enable PA Sync Lost event
Date: Wed, 7 Jan 2026 13:38:04 +0800 [thread overview]
Message-ID: <93015e38-a906-43ff-8b04-921328d351e0@amlogic.com> (raw)
In-Reply-To: <20251219-enable_pa_sync_lost_mask-v1-1-2769917f44e2@amlogic.com>
Hi,
Just a gentle ping regarding this patch.
Best regards,
Yang
> [ EXTERNAL EMAIL ]
>
> From: Yang Li <yang.li@amlogic.com>
>
> Enable the PA Sync Lost event mask to ensure
> PA sync loss is properly reported and handled.
>
> Fixes 59e5396a2579 ("Bluetooth: hci_event: Fix not handling PA Sync Lost event")
>
> Signed-off-by: Yang Li <yang.li@amlogic.com>
> ---
> net/bluetooth/hci_sync.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/net/bluetooth/hci_sync.c b/net/bluetooth/hci_sync.c
> index 5de98be752bc..3f04510b806b 100644
> --- a/net/bluetooth/hci_sync.c
> +++ b/net/bluetooth/hci_sync.c
> @@ -4420,6 +4420,7 @@ static int hci_le_set_event_mask_sync(struct hci_dev *hdev)
> if (bis_capable(hdev)) {
> events[1] |= 0x20; /* LE PA Report */
> events[1] |= 0x40; /* LE PA Sync Established */
> + events[1] |= 0x80; /* LE PA Sync Lost */
> events[3] |= 0x04; /* LE Create BIG Complete */
> events[3] |= 0x08; /* LE Terminate BIG Complete */
> events[3] |= 0x10; /* LE BIG Sync Established */
>
> ---
> base-commit: 98246938a0e66e4100e95b6b7881843a9a4e4882
> change-id: 20251219-enable_pa_sync_lost_mask-ae0fb71f29f3
>
> Best regards,
> --
> Yang Li <yang.li@amlogic.com>
>
>
next prev parent reply other threads:[~2026-01-07 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 2:43 Yang Li via B4 Relay
2026-01-07 5:38 ` Yang Li [this message]
2026-01-07 16:10 ` patchwork-bot+bluetooth
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=93015e38-a906-43ff-8b04-921328d351e0@amlogic.com \
--to=yang.li@amlogic.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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®