From: patchwork-bot+bluetooth@kernel.org
To: Brian Gix <brian.gix@intel.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com
Subject: Re: [PATCH v2 0/3] Clean-up stale/unused hci_request.c code
Date: Fri, 22 Jul 2022 20:10:15 +0000 [thread overview]
Message-ID: <165852061539.17882.14313781188452022391.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220721232225.624426-1-brian.gix@intel.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 21 Jul 2022 16:22:22 -0700 you wrote:
> This will be a growing patch-set of conversions and dead-code removal
> towards the goal of retiring hci_request.c
>
> The patch sets will be split amoung the work queues and delayed work
> queues as initialized in hci_request_setup(), with the ultimate goal of
> eliminating hci_request.c entirely.
>
> [...]
Here is the summary with links:
- [v2,1/3] Bluetooth: Remove dead code from hci_request.c
https://git.kernel.org/bluetooth/bluetooth-next/c/ec2904c259c5
- [v2,2/3] Bluetooth: Remove update_scan hci_request dependancy
https://git.kernel.org/bluetooth/bluetooth-next/c/bb87672562f8
- [v2,3/3] Bluetooth: Convert delayed discov_off to hci_sync
https://git.kernel.org/bluetooth/bluetooth-next/c/0ef08313cefd
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-22 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 23:22 [PATCH v2 0/3] Clean-up stale/unused hci_request.c code Brian Gix
2022-07-21 23:22 ` [PATCH v2 1/3] Bluetooth: Remove dead code from hci_request.c Brian Gix
2022-07-22 0:09 ` Clean-up stale/unused hci_request.c code bluez.test.bot
2022-07-21 23:22 ` [PATCH v2 2/3] Bluetooth: Remove update_scan hci_request dependancy Brian Gix
2022-07-21 23:22 ` [PATCH v2 3/3] Bluetooth: Convert delayed discov_off to hci_sync Brian Gix
2022-07-22 20:10 ` 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=165852061539.17882.14313781188452022391.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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