From: patchwork-bot+bluetooth@kernel.org
To: Manish Mandlik <mmandlik@google.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
chromeos-bluetooth-upstreaming@chromium.org,
linux-bluetooth@vger.kernel.org, mcchou@chromium.org,
davem@davemloft.net, kuba@kernel.org, johan.hedberg@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: msft: Clear tracked devices on resume
Date: Wed, 16 Mar 2022 14:40:10 +0000 [thread overview]
Message-ID: <164744161093.31498.12555709865853013941.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220312020707.1.I2b7f789329979102339d7e0717522ba417b63109@changeid>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Marcel Holtmann <marcel@holtmann.org>:
On Sat, 12 Mar 2022 02:08:58 -0800 you wrote:
> Clear already tracked devices on system resume. Once the monitors are
> reregistered after resume, matched devices in range will be found again.
>
> Signed-off-by: Manish Mandlik <mmandlik@google.com>
> Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
> ---
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: msft: Clear tracked devices on resume
https://git.kernel.org/bluetooth/bluetooth-next/c/28c5124c1e07
- [2/2] Bluetooth: Send AdvMonitor Dev Found for all matched devices
https://git.kernel.org/bluetooth/bluetooth-next/c/1b144a7a0512
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-03-16 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 10:08 Manish Mandlik
2022-03-12 10:08 ` [PATCH 2/2] Bluetooth: Send AdvMonitor Dev Found for all matched devices Manish Mandlik
2022-03-16 14:42 ` Marcel Holtmann
2022-03-16 14:33 ` [PATCH 1/2] Bluetooth: msft: Clear tracked devices on resume Marcel Holtmann
2022-03-16 14:40 ` 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=164744161093.31498.12555709865853013941.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=davem@davemloft.net \
--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@chromium.org \
--cc=mmandlik@google.com \
--cc=netdev@vger.kernel.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®