From: patchwork-bot+bluetooth@kernel.org
To: Manish Mandlik <mmandlik@google.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org,
chromeos-bluetooth-upstreaming@chromium.org, mcchou@google.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
johan.hedberg@gmail.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Bluetooth: hci_sync: Refactor add Adv Monitor
Date: Thu, 21 Jul 2022 21:20:13 +0000 [thread overview]
Message-ID: <165843841384.2414.3327226907905248679.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220720162102.v2.1.If745ed1d05d98c002fc84ba60cef99eb786b7caa@changeid>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 20 Jul 2022 16:21:13 -0700 you wrote:
> Make use of hci_cmd_sync_queue for adding an advertisement monitor.
>
> Signed-off-by: Manish Mandlik <mmandlik@google.com>
> Reviewed-by: Miao-chen Chou <mcchou@google.com>
> ---
>
> Changes in v2:
> - Refactored to correctly use hci_cmd_sync_queue
>
> [...]
Here is the summary with links:
- [v2,1/2] Bluetooth: hci_sync: Refactor add Adv Monitor
https://git.kernel.org/bluetooth/bluetooth-next/c/75d2509cd04e
- [v2,2/2] Bluetooth: hci_sync: Refactor remove Adv Monitor
https://git.kernel.org/bluetooth/bluetooth-next/c/6b88eff43704
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:[~2022-07-21 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 23:21 [PATCH v2 1/2] Bluetooth: hci_sync: Refactor add Adv Monitor Manish Mandlik
2022-07-20 23:21 ` [PATCH v2 2/2] Bluetooth: hci_sync: Refactor remove " Manish Mandlik
2022-07-21 0:09 ` [v2,1/2] Bluetooth: hci_sync: Refactor add " bluez.test.bot
2022-07-21 21:20 ` 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=165843841384.2414.3327226907905248679.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=mcchou@google.com \
--cc=mmandlik@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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