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 v7 0/9] Clean-up stale/unused hci_request.c code
Date: Tue, 09 Aug 2022 22:00:15 +0000 [thread overview]
Message-ID: <166008241553.11039.8770757425299965789.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220805234236.704986-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 Fri, 5 Aug 2022 16:42:27 -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:
- [v7,1/9] Bluetooth: Convert le_scan_disable timeout to hci_sync
https://git.kernel.org/bluetooth/bluetooth-next/c/2bf8edacd155
- [v7,2/9] Bluetooth: Rework le_scan_restart for hci_sync
https://git.kernel.org/bluetooth/bluetooth-next/c/89f043b2c6d5
- [v7,3/9] Bluetooth: Delete unused hci_req_stop_discovery()
https://git.kernel.org/bluetooth/bluetooth-next/c/eed7aab6c517
- [v7,4/9] Bluetooth: Convert SCO configure_datapath to hci_sync
https://git.kernel.org/bluetooth/bluetooth-next/c/71172654bff2
- [v7,5/9] Bluetooth: Move Adv Instance timer to hci_sync
https://git.kernel.org/bluetooth/bluetooth-next/c/8c59889a6b5c
- [v7,6/9] Bluetooth: Delete unreferenced hci_request code
https://git.kernel.org/bluetooth/bluetooth-next/c/3edf244f8c71
- [v7,7/9] Bluetooth: move hci_get_random_address() to hci_sync
https://git.kernel.org/bluetooth/bluetooth-next/c/c7eb26d1285c
- [v7,8/9] Bluetooth: convert hci_update_adv_data to hci_sync
https://git.kernel.org/bluetooth/bluetooth-next/c/9ec46ac996f5
- [v7,9/9] Bluetooth: Convert hci_abort_conn to hci_sync
(no matching commit)
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-08-09 22:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 23:42 [PATCH v7 0/9] Clean-up stale/unused hci_request.c code Brian Gix
2022-08-05 23:42 ` [PATCH v7 1/9] Bluetooth: Convert le_scan_disable timeout to hci_sync Brian Gix
2022-08-06 3:06 ` Clean-up stale/unused hci_request.c code bluez.test.bot
2022-08-05 23:42 ` [PATCH v7 2/9] Bluetooth: Rework le_scan_restart for hci_sync Brian Gix
2022-08-05 23:42 ` [PATCH v7 3/9] Bluetooth: Delete unused hci_req_stop_discovery() Brian Gix
2022-08-05 23:42 ` [PATCH v7 4/9] Bluetooth: Convert SCO configure_datapath to hci_sync Brian Gix
2022-08-05 23:42 ` [PATCH v7 5/9] Bluetooth: Move Adv Instance timer " Brian Gix
2022-08-05 23:42 ` [PATCH v7 6/9] Bluetooth: Delete unreferenced hci_request code Brian Gix
2022-08-05 23:42 ` [PATCH v7 7/9] Bluetooth: move hci_get_random_address() to hci_sync Brian Gix
2022-08-05 23:42 ` [PATCH v7 8/9] Bluetooth: convert hci_update_adv_data " Brian Gix
2022-08-05 23:42 ` [PATCH v7 9/9] Bluetooth: Convert hci_abort_conn " Brian Gix
2022-08-09 22:00 ` 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=166008241553.11039.8770757425299965789.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