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-06-01
Date: Mon, 2 Jun 2014 11:06:36 -0300 [thread overview]
Message-ID: <20140602140636.GA1659@joana> (raw)
[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]
Hi John,
Here some more patches for 3.16. We know that Linus already opened the merge
window, but this is fix only pull request, and most of the patches here are
also tagged for stable.
Please pull! or let me know of any issues. Thanks!
Gustavo
---
The following changes since commit d7b2545023ecfde94d3ea9c03c5480ac18da96c9:
Bluetooth: Clearly distinguish mgmt LTK type from authenticated property (2014-05-23 11:24:04 -0700)
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 8a96f3cd22878fc0bb564a8478a6e17c0b8dca73:
Bluetooth: Fix L2CAP deadlock (2014-06-02 13:38:19 +0300)
----------------------------------------------------------------
Adam Lee (1):
Bluetooth: ath3k: no need to set same pipe multiple times
Johan Hedberg (4):
Bluetooth: Fix properly ignoring LTKs of unknown types
Bluetooth: Fix authentication check for FIPS security level
Bluetooth: Fix requiring SMP MITM for outgoing connections
Bluetooth: Fix missing check for FIPS security level
Jukka Rissanen (2):
Bluetooth: 6LoWPAN: Fix MAC address universal/local bit handling
Bluetooth: l2cap: Set more channel defaults
Jukka Taimisto (1):
Bluetooth: Fix L2CAP deadlock
drivers/bluetooth/ath3k.c | 3 ++-
net/bluetooth/6lowpan.c | 65 +++++++++++++++++++++++++++++-------------------------
net/bluetooth/hci_event.c | 4 +++-
net/bluetooth/l2cap_core.c | 6 +++++
net/bluetooth/l2cap_sock.c | 5 ++++-
net/bluetooth/mgmt.c | 10 +++++++--
net/bluetooth/smp.c | 7 +++---
7 files changed, 62 insertions(+), 38 deletions(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-06-02 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 14:06 Gustavo Padovan [this message]
2014-06-05 18:10 ` pull request: bluetooth-next 2014-06-01 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=20140602140636.GA1659@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).