From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Bluetooth: hci_conn: Fix not cleaning up on LE Connection failure
Date: Tue, 28 Mar 2023 20:30:18 +0000 [thread overview]
Message-ID: <168003541817.31334.5504159368010073543.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230327205347.51568-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 Mon, 27 Mar 2023 13:53:46 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> hci_connect_le_scan_cleanup shall always be invoked to cleanup the
> states and re-enable passive scanning if necessary, otherwise it may
> cause the pending action to stay active causing multiple attempts to
> connect.
>
> [...]
Here is the summary with links:
- [v2,1/2] Bluetooth: hci_conn: Fix not cleaning up on LE Connection failure
https://git.kernel.org/bluetooth/bluetooth-next/c/501ba6f31a83
- [v2,2/2] Bluetooth: Fix printing errors if LE Connection times out
https://git.kernel.org/bluetooth/bluetooth-next/c/2731e038a76d
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:[~2023-03-28 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 20:53 [PATCH v2 1/2] Bluetooth: hci_conn: Fix not cleaning up on LE Connection failure Luiz Augusto von Dentz
2023-03-27 20:53 ` [PATCH v2 2/2] Bluetooth: Fix printing errors if LE Connection times out Luiz Augusto von Dentz
2023-03-29 8:58 ` Ahmad Fatoum
2023-03-27 21:38 ` [v2,1/2] Bluetooth: hci_conn: Fix not cleaning up on LE Connection failure bluez.test.bot
2023-03-28 20: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=168003541817.31334.5504159368010073543.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.