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 2012-05-04
Date: Fri, 4 May 2012 21:12:43 -0300 [thread overview]
Message-ID: <20120505001243.GC23728@joana> (raw)
[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]
Hi John,
A few more patch to 3.4. There is 3 fixes from Mat Martineau, a fix for
a incoming MTU check that was breaking ERTM, still on ERTM there is a
patch that fixes concurrency with one of our locks. His third patch is
related to lock fixes too.
Besides that Johan fixed a wrong bit set in the Inquiry code, Vishal
Agarwal added a EIR fix and finally we have support for one more usb id.
Please pull or let me know of any problems!
Gustavo
---
The following changes since commit 985140369be1e886754d8ac0375dd64e4f727311:
Add Foxconn / Hon Hai IDs for btusb module (2012-04-24 11:38:41 -0300)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth for-upstream
for you to fetch changes up to 78521bdb4a42770c4c2d48317c00ec0d7f451a08:
Bluetooth: Lock the L2CAP channel when sending (2012-05-04 20:56:29 -0300)
----------------------------------------------------------------
Johan Hedberg (1):
Bluetooth: Fix Inquiry with RSSI event mask
Mat Martineau (3):
Bluetooth: Fix a redundant and problematic incoming MTU check
Bluetooth: Restore locking semantics when looking up L2CAP channels
Bluetooth: Lock the L2CAP channel when sending
Michael Gruetzner (1):
bluetooth: Add support for Foxconn/Hon Hai AR5BBU22 0489:E03C
Vishal Agarwal (1):
Bluetooth: Fix EIR data generation for mgmt_device_found
drivers/bluetooth/ath3k.c | 6 ++++++
drivers/bluetooth/btusb.c | 3 +++
include/net/bluetooth/bluetooth.h | 2 --
include/net/bluetooth/hci_core.h | 17 +++++++++++++++++
net/bluetooth/hci_event.c | 6 ++++--
net/bluetooth/l2cap_core.c | 30 +++---------------------------
net/bluetooth/l2cap_sock.c | 19 +++++++++++--------
7 files changed, 44 insertions(+), 39 deletions(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-05-05 0:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 0:12 Gustavo Padovan [this message]
2012-05-08 7:07 ` pull request: bluetooth 2012-05-04 Gustavo Padovan
2012-05-11 20:16 ` Gustavo Padovan
2012-05-12 18:22 ` John W. Linville
2012-05-12 19:09 ` Gustavo Padovan
2012-05-12 19:11 ` [PATCH 1/2] Bluetooth: notify userspace of security level change Gustavo Padovan
2012-05-12 19:11 ` [PATCH 2/2] Bluetooth: mgmt: Fix device_connected sending order Gustavo Padovan
2012-05-13 6:20 ` [PATCH 1/2] Bluetooth: notify userspace of security level change Gustavo Padovan
2012-05-14 16:22 ` valdis.kletnieks
2012-05-13 6:22 ` Gustavo Padovan
2012-05-13 4:31 ` pull request: bluetooth 2012-05-04 Johan Hedberg
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=20120505001243.GC23728@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).