From: Gustavo Padovan <gustavo@padovan.org>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: pull request: bluetooth-next 2013-04-23
Date: Tue, 23 Apr 2013 20:58:25 -0300 [thread overview]
Message-ID: <20130423235825.GG1697@joana> (raw)
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
Hi John,
A few more patches intended for 3.10, the most important one is the support in
btusb for fw loading for the Intel Bluetooth device. Other than that we have
only fixes and clean ups.
Please pull or let me know of any problems! Thanks.
Gustavo
---
The following changes since commit 76a388beaf92cc75b829d4a0b7d69afaaeaa4b0a:
Bluetooth: Rename LE_SCANNING_* macros (2013-04-18 01:17:27 -0300)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next for-upstream
for you to fetch changes up to 69676b1c2af451bfe5cd36ff4973a484b5d5a86c:
Bluetooth: btmrvl: report error if verify_fw_download times out (2013-04-23 20:55:55 -0300)
----------------------------------------------------------------
Andreas Fenkart (2):
Bluetooth: btmrvl: release lock while waiting for fw download complete
Bluetooth: btmrvl: report error if verify_fw_download times out
Andy Shevchenko (1):
Bluetooth: btmrvl: use native helpers for debugfs
Fengguang Wu (1):
Bluetooth: hci_get_cmd_complete() can be static
Gustavo Padovan (1):
Bluetooth: remove unneeded var initialization in btmrvl
Johan Hedberg (2):
Bluetooth: Fix HCI command send functions to use const specifier
Bluetooth: Fix sending write_le_host_supporte for LE-only controllers
Marcel Holtmann (1):
Bluetooth: Remove unneeded parameter from L2CAP ATT channel handling
Tedd Ho-Jeong An (1):
Bluetooth: Add support for Intel Bluetooth device [8087:07dc]
drivers/bluetooth/btmrvl_debugfs.c | 266 +++------------------------
drivers/bluetooth/btmrvl_sdio.c | 41 +++--
drivers/bluetooth/btusb.c | 377 +++++++++++++++++++++++++++++++++++++++
include/net/bluetooth/hci_core.h | 14 +-
net/bluetooth/hci_core.c | 29 ++-
net/bluetooth/l2cap_core.c | 7 +-
net/bluetooth/mgmt.c | 8 +-
7 files changed, 462 insertions(+), 280 deletions(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2013-04-23 23:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130423235825.GG1697@joana \
--to=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox