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 2014-05-26
Date: Mon, 26 May 2014 18:41:22 -0300 [thread overview]
Message-ID: <20140526214122.GA2034@joana> (raw)
[-- Attachment #1: Type: text/plain, Size: 2667 bytes --]
Hi John,
Some more patches for 3.16. There is nothing really special here, just a
bunch of clean ups, fixes plus some small improvements. Please pull.
Thanks!
Gustavo
---
The following changes since commit 22e70786413ed05950207eda7be420c280b776d7:
Bluetooth: Remove hci_h4 unused defines (2014-04-24 11:55:26 -0300)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git for-upstream
for you to fetch changes up to d7b2545023ecfde94d3ea9c03c5480ac18da96c9:
Bluetooth: Clearly distinguish mgmt LTK type from authenticated property (2014-05-23 11:24:04 -0700)
----------------------------------------------------------------
Andrzej Kaczmarek (8):
Bluetooth: Store RSSI for connection
Bluetooth: Store TX power level for connection
Bluetooth: Add conn info lifetime parameters to debugfs
Bluetooth: Add support to get connection information
Bluetooth: Avoid polling TX power for LE links
Bluetooth: Store max TX power level for connection
Bluetooth: Add support for max_tx_power in Get Conn Info
Bluetooth: Add missing msecs to jiffies conversion
Johan Hedberg (8):
Bluetooth: Add support for SMP Invalid Parameters error code
Bluetooth: Make SMP context private to smp.c
Bluetooth: Fix setting initial local auth_req value
Bluetooth: Remove unnecessary work structs from SMP code
Bluetooth: Rename smp->smp_flags to smp->flags
Bluetooth: Update smp_random to return a response code
Bluetooth: Update smp_confirm to return a response code
Bluetooth: Clearly distinguish mgmt LTK type from authenticated property
Libor Pechacek (1):
Bluetooth: Convert RFCOMM spinlocks into mutexes
Marcel Holtmann (1):
Bluetooth: Increment management interface revision
Petri Gynther (1):
Bluetooth: btusb: Add Broadcom patch RAM support
drivers/bluetooth/btusb.c | 155 ++++++++++++++++++++++++++++++-
include/net/bluetooth/hci.h | 21 +++++
include/net/bluetooth/hci_core.h | 11 +++
include/net/bluetooth/mgmt.h | 15 +++
include/net/bluetooth/rfcomm.h | 6 +-
net/bluetooth/hci_conn.c | 3 +
net/bluetooth/hci_core.c | 64 +++++++++++++
net/bluetooth/hci_event.c | 61 +++++++++++++
net/bluetooth/mgmt.c | 236 +++++++++++++++++++++++++++++++++++++++++++++++-
net/bluetooth/rfcomm/core.c | 2 +-
net/bluetooth/rfcomm/tty.c | 20 ++--
net/bluetooth/smp.c | 153 +++++++++++++++----------------
net/bluetooth/smp.h | 30 +-----
13 files changed, 653 insertions(+), 124 deletions(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-05-26 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 21:41 Gustavo Padovan [this message]
2014-05-29 17:04 ` pull request: bluetooth-next 2014-05-26 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=20140526214122.GA2034@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).