From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, brian.gix@intel.com
Subject: [PATCH v4 0/4] Clean-up stale/unused hci_request.c code
Date: Wed, 27 Jul 2022 06:58:30 -0700 [thread overview]
Message-ID: <20220727135834.294184-1-brian.gix@intel.com> (raw)
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.
v2: Published
v3: Continuing work. This does include one conversion
(SCO configure_datapath) that has been tested with mgmt-tester and
sco-tester, but has not been tested with a controller with an
off-loadable codec.
v4: Clean-up checkpatch warnings.
Brian Gix (4):
Bluetooth: Convert le_scan_disable timeout to hci_sync
Bluetooth: Rework le_scan_restart for hci_sync
Bluetooth: Delete unused hci_req_stop_discovery()
Bluetooth: Convert SCO configure_datapath to hci_sync
net/bluetooth/hci_conn.c | 86 +++++++++--
net/bluetooth/hci_request.c | 282 +-----------------------------------
net/bluetooth/hci_request.h | 4 -
net/bluetooth/hci_sync.c | 148 +++++++++++++++++++
4 files changed, 224 insertions(+), 296 deletions(-)
--
2.37.1
next reply other threads:[~2022-07-27 13:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 13:58 Brian Gix [this message]
2022-07-27 13:58 ` [PATCH v4 1/4] Bluetooth: Convert le_scan_disable timeout to hci_sync Brian Gix
2022-07-27 14:30 ` Clean-up stale/unused hci_request.c code bluez.test.bot
2022-07-27 13:58 ` [PATCH v4 2/4] Bluetooth: Rework le_scan_restart for hci_sync Brian Gix
2023-06-15 12:06 ` Stefan Agner
2023-06-15 12:47 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-06-15 14:47 ` Jan Čermák
2023-06-15 17:27 ` Luiz Augusto von Dentz
2023-06-15 18:28 ` Luiz Augusto von Dentz
[not found] ` <CABUQxGxBdAFncJ6YVb7a9gnU-_YZDGFDmpHJTtm5K1tDGEGRDQ@mail.gmail.com>
2023-06-20 14:41 ` Stefan Agner
2023-06-30 10:59 ` Stefan Agner
2023-08-29 11:22 ` Linux regression tracking (Thorsten Leemhuis)
2023-08-29 13:27 ` Stefan Agner
2023-08-29 14:34 ` Linux regression tracking (Thorsten Leemhuis)
2023-08-29 20:42 ` Luiz Augusto von Dentz
2023-08-30 17:28 ` Luiz Augusto von Dentz
2023-08-30 20:31 ` Stefan Agner
2022-07-27 13:58 ` [PATCH v4 3/4] Bluetooth: Delete unused hci_req_stop_discovery() Brian Gix
2022-07-27 13:58 ` [PATCH v4 4/4] Bluetooth: Convert SCO configure_datapath to hci_sync Brian Gix
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=20220727135834.294184-1-brian.gix@intel.com \
--to=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;
as well as URLs for NNTP newsgroup(s).