linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2013-07-30
Date: Tue, 30 Jul 2013 13:38:48 +0100	[thread overview]
Message-ID: <20130730123848.GE5975@joana> (raw)

[-- Attachment #1: Type: text/plain, Size: 2291 bytes --]

Hi John,

A few fixes and devices ID additions for 3.11: 

 * There are 4 new ath3k device ids 
 * Fixed stack memory usage in ath3k.
 * Fixed the init process of BlueFRITZ! devices, they were failing to init
   due to an unsupported command we sent. 
 * Fixed wrong use of PTR_ERR in btusb code that was preventing intel devices
   to work properly.
 * Fixed race condition between hci_register_dev() and hci_dev_open() that
   could cause a NULL pointer dereference.
 * Fixed race condition that could call hci_req_cmd_complete() and make some
   devices to fail as showed in the log added to the commit message.

Please pull or let me know of any issues. Thanks.

	Gustavo

--
The following changes since commit 075163bbb0f51174359947e1bce84f5edb23f21e:

  ath9k_htc: Handle IDLE state transition properly (2013-06-24 13:52:52 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth master

for you to fetch changes up to 53e21fbc288218a423959f878c86471a0e323a9a:

  Bluetooth: Fix calling request callback more than once (2013-07-29 12:28:04 +0100)

----------------------------------------------------------------
AceLan Kao (2):
      Bluetooth: Add support for Atheros [0cf3:3121]
      Bluetooth: Add support for Atheros [0cf3:e003]

Adam Lee (1):
      Bluetooth: fix wrong use of PTR_ERR() in btusb

Gustavo Padovan (1):
      Bluetooth: Fix race between hci_register_dev() and hci_dev_open()

Jaganath Kanakkassery (1):
      Bluetooth: Fix invalid length check in l2cap_information_rsp()

Johan Hedberg (2):
      Bluetooth: Fix HCI init for BlueFRITZ! devices
      Bluetooth: Fix calling request callback more than once

Stanislaw Gruszka (1):
      Bluetooth: ath3k: don't use stack memory for DMA

Sujith Manoharan (1):
      Bluetooth: ath3k: Add support for ID 0x13d3/0x3402

Thomas Loo (1):
      Bluetooth: ath3k: Add support for Fujitsu Lifebook UH5x2 [04c5:1330]

 drivers/bluetooth/ath3k.c  | 46 +++++++++++++++++++++++++++++++++++++---------
 drivers/bluetooth/btusb.c  | 18 +++++++++++-------
 net/bluetooth/hci_core.c   | 26 +++++++++++++++++---------
 net/bluetooth/l2cap_core.c |  2 +-
 4 files changed, 66 insertions(+), 26 deletions(-)

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-07-30 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 12:38 Gustavo Padovan [this message]
2013-07-31 19:08 ` pull request: bluetooth 2013-07-30 John W. Linville

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=20130730123848.GE5975@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;
as well as URLs for NNTP newsgroup(s).