From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v5 1/2] Bluetooth: hci_sync: Use address filtering when HCI_PA_SYNC is set
Date: Tue, 27 Feb 2024 16:30:32 +0000 [thread overview]
Message-ID: <170905143219.12854.3853401443050927923.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240227151537.1884044-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 27 Feb 2024 10:15:36 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> If HCI_PA_SYNC flag is set it means there is a Periodic Advertising
> Synchronization pending, so this attempts to locate the address passed
> to HCI_OP_LE_PA_CREATE_SYNC and program it in the accept list so only
> reports with that address are processed.
>
> [...]
Here is the summary with links:
- [v5,1/2] Bluetooth: hci_sync: Use address filtering when HCI_PA_SYNC is set
https://git.kernel.org/bluetooth/bluetooth-next/c/7e2b80470c5a
- [v5,2/2] Bluetooth: hci_sync: Use QoS to determine which PHY to scan
https://git.kernel.org/bluetooth/bluetooth-next/c/715b938b3a0f
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:[~2024-02-27 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 15:15 [PATCH v5 1/2] Bluetooth: hci_sync: Use address filtering when HCI_PA_SYNC is set Luiz Augusto von Dentz
2024-02-27 15:15 ` [PATCH v5 2/2] Bluetooth: hci_sync: Use QoS to determine which PHY to scan Luiz Augusto von Dentz
2024-02-27 15:59 ` [v5,1/2] Bluetooth: hci_sync: Use address filtering when HCI_PA_SYNC is set bluez.test.bot
2024-02-27 16:30 ` 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=170905143219.12854.3853401443050927923.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).