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-03-24
Date: Mon, 24 Mar 2014 14:33:32 -0300 [thread overview]
Message-ID: <20140324173332.GA2214@joana> (raw)
[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]
Hi John,
Here follow another set of patches to 3.15. This is mostly a bug fix pull
request with the exception of one commit from Marcel which adds tracking to
the current configured LE scan type parameter.
Please pull or let me know of any issues. Thanks!
Gustavo
---
The following changes since commit 40b552aa5a0bfa785bc7ddb5c2d7965b1e0bb08d:
Bluetooth: Enforce strict Secure Connections Only mode security (2014-03-19 23:30:32 +0200)
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 8396215d4865d66be9cdfcec8d135862e1fd98d1:
Bluetooth: Remove unnecessary assignment in SMP (2014-03-24 08:43:50 -0700)
----------------------------------------------------------------
Amitkumar Karwar (1):
Bluetooth: btmrvl: don't consume all vendor specific events
Johan Hedberg (10):
Bluetooth: Fix passkey endianess in user_confirm and notify_passkey
Bluetooth: Fix address value for early disconnection events
Bluetooth: Fix potential NULL pointer dereference in SMP
Bluetooth: Add missing cmd_status handler for LE_Start_Encryption
Bluetooth: Fix SMP confirmation callback handling
Bluetooth: Add SMP flag to track which side is the initiator
Bluetooth: Don't try to confirm locally initiated SMP pairing
Bluetooth: Remove LTK re-encryption procedure
Bluetooth: Fix potential NULL pointer dereference in smp_conn_security
Bluetooth: Remove unnecessary assignment in SMP
Marcel Holtmann (1):
Bluetooth: Track current configured LE scan type parameter
Thomas Gleixner (1):
Bluetooth: bluecard: Use del_timer_sync() in teardown path
drivers/bluetooth/bluecard_cs.c | 2 +-
drivers/bluetooth/btmrvl_main.c | 11 +++---
include/net/bluetooth/hci_core.h | 3 +-
net/bluetooth/hci_event.c | 63 +++++++++++++++++++++++++++++++-
net/bluetooth/mgmt.c | 20 ++--------
net/bluetooth/smp.c | 87 ++++++++++++++++++--------------------------
net/bluetooth/smp.h | 7 +---
7 files changed, 111 insertions(+), 82 deletions(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-03-24 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 17:33 Gustavo Padovan [this message]
2014-03-26 18:34 ` pull request: bluetooth-next 2014-03-24 Gustavo Padovan
2014-03-27 18:18 ` 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=20140324173332.GA2214@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).