From: Johan Hedberg <johan.hedberg@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v2 00/11] Bluetooth: Add asynchronous request support
Date: Tue, 5 Mar 2013 10:28:59 +0200 [thread overview]
Message-ID: <1362472150-30965-1-git-send-email-johan.hedberg@gmail.com> (raw)
Hi,
Here's a v2 of the patch set with previous feedback taken into account.
One notable thing is with the request complete callback where I decided
after all to ommit the last_opcode parameter. The reason for this is
that it is indeed only used for logging in subsequent patches which is a
bit redundant with the logs already existing in the other functions
leading to the complete callback, and the same info is also available
with tools like btmon. Furthermore, if some future piece of code really
does end up needing this info it can always be dug out from
hdev->sent_cmd.
Johan
----------------------------------------------------------------
Johan Hedberg (11):
Bluetooth: Rename hci_request to hci_req_sync
Bluetooth: Fix __hci_request() handling of empty requests
Bluetooth: Split HCI init sequence into three stages
Bluetooth: Add initial skeleton for asynchronous HCI requests
Bluetooth: Refactor HCI command skb creation
Bluetooth: Introduce new hci_req_add function
Bluetooth: Introduce a hci_req_from_skb function
Bluetooth: Add request cmd_complete and cmd_status functions
Bluetooth: Use async requests internally in hci_req_sync
Bluetooth: Remove unused hdev->init_last_cmd
Bluetooth: Remove empty HCI event handlers
include/net/bluetooth/bluetooth.h | 10 +
include/net/bluetooth/hci_core.h | 16 +-
net/bluetooth/hci_core.c | 673 +++++++++++++++++++++++++++++++------
net/bluetooth/hci_event.c | 504 +--------------------------
net/bluetooth/hci_sock.c | 3 +-
5 files changed, 603 insertions(+), 603 deletions(-)
next reply other threads:[~2013-03-05 8:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 8:28 Johan Hedberg [this message]
2013-03-05 8:29 ` [PATCH v2 01/11] Bluetooth: Rename hci_request to hci_req_sync Johan Hedberg
2013-03-05 8:29 ` [PATCH v2 02/11] Bluetooth: Fix __hci_request() handling of empty requests Johan Hedberg
2013-03-05 8:29 ` [PATCH v2 03/11] Bluetooth: Split HCI init sequence into three stages Johan Hedberg
2013-03-05 17:01 ` Marcel Holtmann
2013-03-05 8:29 ` [PATCH v2 04/11] Bluetooth: Add initial skeleton for asynchronous HCI requests Johan Hedberg
2013-03-05 8:29 ` [PATCH v2 05/11] Bluetooth: Refactor HCI command skb creation Johan Hedberg
2013-03-05 8:29 ` [PATCH v2 06/11] Bluetooth: Introduce new hci_req_add function Johan Hedberg
2013-03-05 8:29 ` [PATCH v2 07/11] Bluetooth: Introduce a hci_req_from_skb function Johan Hedberg
2013-03-05 17:04 ` Marcel Holtmann
2013-03-05 8:29 ` [PATCH v2 08/11] Bluetooth: Add request cmd_complete and cmd_status functions Johan Hedberg
2013-03-05 8:29 ` [PATCH v2 09/11] Bluetooth: Use async requests internally in hci_req_sync Johan Hedberg
2013-03-05 17:08 ` Marcel Holtmann
2013-03-05 8:29 ` [PATCH v2 10/11] Bluetooth: Remove unused hdev->init_last_cmd Johan Hedberg
2013-03-05 8:29 ` [PATCH v2 11/11] Bluetooth: Remove empty HCI event handlers Johan Hedberg
2013-03-05 17:10 ` Marcel Holtmann
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=1362472150-30965-1-git-send-email-johan.hedberg@gmail.com \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.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