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 2012-05-02
Date: Wed, 2 May 2012 19:49:25 -0300 [thread overview]
Message-ID: <20120502222749.GD16030@joana> (raw)
[-- Attachment #1: Type: text/plain, Size: 3135 bytes --]
Hi John,
Another set of changes to the 3.5 kernel. The main changes here are in the LE
code, by Andre Guedes and in the L2CAP ERTM implementation by Mat Martineau.
The rest of the patches are just clean up and small fixes.
Please pull!
Gustavo
---
The following changes since commit 11069ef318f92fb5960ebd7f9c01e5bc0dcb63fc:
mac80211: don't transmit 40MHz frames to 20MHz peer (2012-04-27 16:07:24 -0400)
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 6bed2e71fa55572b6e1355594a119e54b20eb426:
bluetooth: Add support for Foxconn/Hon Hai AR5BBU22 0489:E03C (2012-05-02 18:13:29 -0300)
----------------------------------------------------------------
Amitkumar Karwar (1):
Bluetooth: btmrvl: configure default host sleep parameters
Andre Guedes (9):
Bluetooth: Remove useless code in hci_connect
Bluetooth: Move address type macros to bluetooth.h
Bluetooth: Rename link_to_mgmt to link_to_bdaddr
Bluetooth: Rename mgmt_to_le to bdaddr_to_le
Bluetooth: Add address type to struct sockaddr_l2
Bluetooth: Move bdaddr_to_le to hci_core
Bluetooth: Add dst_type parameter to hci_connect
Bluetooth: Use address type info from user-space
Bluetooth: Remove advertising cache
Gustavo Padovan (1):
Bluetooth: Remove unneeded elements from size calculation
Johan Hedberg (1):
Bluetooth: Fix Inquiry with RSSI event mask
Mat Martineau (8):
Bluetooth: Improve ERTM sequence number offset calculation
Bluetooth: Remove duplicate structure members from bt_skb_cb
Bluetooth: Move recently-added ERTM header packing functions
Bluetooth: Move recently-added ERTM header unpacking functions
Bluetooth: Initialize new l2cap_chan structure members
Bluetooth: Remove unused function
Bluetooth: Make better use of l2cap_chan reference counting
Bluetooth: Add Code Aurora Forum copyright
Michael Gruetzner (1):
bluetooth: Add support for Foxconn/Hon Hai AR5BBU22 0489:E03C
Syam Sidhardhan (1):
Bluetooth: Remove unused hci_le_ltk_reply()
Vishal Agarwal (1):
Bluetooth: Fix EIR data generation for mgmt_device_found
drivers/bluetooth/ath3k.c | 6 +
drivers/bluetooth/btmrvl_drv.h | 1 +
drivers/bluetooth/btmrvl_main.c | 53 ++++---
drivers/bluetooth/btmrvl_sdio.c | 3 +
drivers/bluetooth/btusb.c | 3 +
include/net/bluetooth/bluetooth.h | 8 +-
include/net/bluetooth/hci_core.h | 47 ++++---
include/net/bluetooth/l2cap.h | 14 +-
net/bluetooth/hci_conn.c | 30 +---
net/bluetooth/hci_core.c | 86 ++----------
net/bluetooth/hci_event.c | 13 +-
net/bluetooth/l2cap_core.c | 294 ++++++++++++++++++++-------------------
net/bluetooth/l2cap_sock.c | 5 +-
net/bluetooth/mgmt.c | 78 +++++------
net/bluetooth/sco.c | 3 +-
15 files changed, 289 insertions(+), 355 deletions(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2012-05-02 22:49 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=20120502222749.GD16030@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).