From: Gustavo Padovan <gustavo@padovan.org>
To: linville@tuxdriver.com, davem@davemloft.net
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: pull request: bluetooth-next 2012-11-20
Date: Tue, 20 Nov 2012 20:08:42 -0200 [thread overview]
Message-ID: <20121120220842.GA15370@joana> (raw)
[-- Attachment #1: Type: text/plain, Size: 2250 bytes --]
Hi John,
A few patches to 3.8. The majority of the work here is from Andrei on the High
Speed support. Other than that Johan added support for setting LE advertising
data. The rest are fixes and clean ups and small improvements like support for
a new broadcom hardware.
Gustavo
---
The following changes since commit 57527f8d4d71b5167a02fb6713857f55d3974748:
ath9k_hw: Program filter coefficients correctly (2012-11-16 14:29:11 -0500)
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 2b2fec4d08a0aabe20d2e749cb7978f04217af65:
Bluetooth: Remove OOB data if device was discovered in band (2012-11-20 16:03:15 -0200)
----------------------------------------------------------------
Andrei Emeltchenko (9):
Bluetooth: Use __l2cap_no_conn_pending helper
Bluetooth: Remove unneeded local_amp_id initialization
Bluetooth: Refactor locking in amp_physical_cfm
Bluetooth: Disable FCS only for new HS channels
Bluetooth: trivial: Use __constant for constants
Bluetooth: Fix sending L2CAP Create Chan Req
Bluetooth: Set local_amp_id after getting Phylink Completed evt
Bluetooth: Improve error message printing
Bluetooth: AMP: Set no FCS for incoming L2CAP chan
Jeff Cook (1):
Bluetooth: Add support for BCM20702A0 [0b05, 17b5]
Johan Hedberg (3):
Bluetooth: Use proper invalid value for tx_power
Bluetooth: Add support for setting LE advertising data
Bluetooth: Fix updating advertising state flags and data
Szymon Janc (2):
Bluetooth: Increase HCI command tx timeout
Bluetooth: Remove OOB data if device was discovered in band
drivers/bluetooth/btusb.c | 1 +
include/net/bluetooth/hci.h | 22 +++++++++-
include/net/bluetooth/hci_core.h | 4 ++
include/net/bluetooth/l2cap.h | 2 +-
net/bluetooth/amp.c | 8 +++-
net/bluetooth/hci_core.c | 98 ++++++++++++++++++++++++++++++++++++++++++
net/bluetooth/hci_event.c | 44 ++++++++++++++++++-
net/bluetooth/l2cap_core.c | 52 ++++++++++++----------
net/bluetooth/mgmt.c | 2 +-
9 files changed, 204 insertions(+), 29 deletions(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2012-11-20 22:08 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=20121120220842.GA15370@joana \
--to=gustavo@padovan.org \
--cc=davem@davemloft.net \
--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).