From: patchwork-bot+bluetooth@kernel.org
To: Yang Li <yang.li@amlogic.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: Prevent unintended pause by checking if advertising is active
Date: Mon, 23 Jun 2025 19:10:21 +0000 [thread overview]
Message-ID: <175070582174.3268784.13178824163503894231.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250619-bluetooth_adv-v2-1-4bfc32941e53@amlogic.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 19 Jun 2025 11:01:07 +0800 you wrote:
> From: Yang Li <yang.li@amlogic.com>
>
> When PA Create Sync is enabled, advertising resumes unexpectedly.
> Therefore, it's necessary to check whether advertising is currently
> active before attempting to pause it.
>
> < HCI Command: LE Add Device To... (0x08|0x0011) plen 7 #1345 [hci0] 48.306205
> Address type: Random (0x01)
> Address: 4F:84:84:5F:88:17 (Resolvable)
> Identity type: Random (0x01)
> Identity: FC:5B:8C:F7:5D:FB (Static)
> < HCI Command: LE Set Address Re.. (0x08|0x002d) plen 1 #1347 [hci0] 48.308023
> Address resolution: Enabled (0x01)
> ...
> < HCI Command: LE Set Extended A.. (0x08|0x0039) plen 6 #1349 [hci0] 48.309650
> Extended advertising: Enabled (0x01)
> Number of sets: 1 (0x01)
> Entry 0
> Handle: 0x01
> Duration: 0 ms (0x00)
> Max ext adv events: 0
> ...
> < HCI Command: LE Periodic Adve.. (0x08|0x0044) plen 14 #1355 [hci0] 48.314575
> Options: 0x0000
> Use advertising SID, Advertiser Address Type and address
> Reporting initially enabled
> SID: 0x02
> Adv address type: Random (0x01)
> Adv address: 4F:84:84:5F:88:17 (Resolvable)
> Identity type: Random (0x01)
> Identity: FC:5B:8C:F7:5D:FB (Static)
> Skip: 0x0000
> Sync timeout: 20000 msec (0x07d0)
> Sync CTE type: 0x0000
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: Prevent unintended pause by checking if advertising is active
https://git.kernel.org/bluetooth/bluetooth-next/c/8466ce07cb6a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-06-23 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 3:01 Yang Li via B4 Relay
2025-06-23 19:10 ` patchwork-bot+bluetooth [this message]
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=175070582174.3268784.13178824163503894231.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--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 \
--cc=yang.li@amlogic.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
all inboxes | Powered by JetHome®