From: patchwork-bot+bluetooth@kernel.org
To: Abhishek Pandit-Subedi <abhishekpandit@google.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, abhishekpandit@chromium.org,
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 1/2] Bluetooth: Fix index added after unregister
Date: Sun, 05 Jun 2022 04:50:12 +0000 [thread overview]
Message-ID: <165440461282.31102.17462326993445996139.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220602094645.1.I7d191480c15b45a237b927e26aa26ba806409efb@changeid>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Marcel Holtmann <marcel@holtmann.org>:
On Thu, 2 Jun 2022 09:46:49 -0700 you wrote:
> From: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
>
> When a userchannel socket is released, we should check whether the hdev
> is already unregistered before sending out an IndexAdded.
>
> Signed-off-by: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: Fix index added after unregister
https://git.kernel.org/bluetooth/bluetooth-next/c/8d4b73539cca
- [2/2] Bluetooth: Unregister suspend with userchannel
https://git.kernel.org/bluetooth/bluetooth-next/c/d6bb2a91f95b
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-06-05 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 16:46 Abhishek Pandit-Subedi
2022-06-02 16:46 ` [PATCH 2/2] Bluetooth: Unregister suspend with userchannel Abhishek Pandit-Subedi
2022-06-05 4:50 ` 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=165440461282.31102.17462326993445996139.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=abhishekpandit@google.com \
--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=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
all inboxes | Powered by JetHome®