From: Marcel Holtmann <marcel@holtmann.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Pull request: bluetooth-2.6 2010-07-08
Date: Thu, 8 Jul 2010 20:40:50 -0300 [thread overview]
Message-ID: <cover.1278632276.git.marcel@holtmann.org> (raw)
Hi Dave,
so I took the two security fixes and the interoperability fix for basic
mode L2CAP connections and combined them here.
All the other patches where bug fixes with L2CAP ERTM support and I will
send them separately.
Regards
Marcel
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git master
This will update the following files:
net/bluetooth/hci_conn.c | 5 +++++
net/bluetooth/hci_event.c | 2 ++
net/bluetooth/l2cap.c | 14 +++++++++++---
3 files changed, 18 insertions(+), 3 deletions(-)
through these ChangeSets:
Andrei Emeltchenko (1):
Bluetooth: Check L2CAP pending status before sending connect request
Johan Hedberg (1):
Bluetooth: Reset the security level after an authentication failure
Ville Tervo (1):
Bluetooth: Update sec_level/auth_type for already existing connections
next reply other threads:[~2010-07-08 23:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 23:40 Marcel Holtmann [this message]
2010-07-08 23:40 ` [PATCH 1/3] Bluetooth: Check L2CAP pending status before sending connect request Marcel Holtmann
2010-07-08 23:40 ` [PATCH 2/3] Bluetooth: Reset the security level after an authentication failure Marcel Holtmann
2010-07-08 23:40 ` [PATCH 3/3] Bluetooth: Update sec_level/auth_type for already existing connections Marcel Holtmann
2010-07-09 0:28 ` Pull request: bluetooth-2.6 2010-07-08 David Miller
-- strict thread matches above, loose matches on Subject: below --
2010-07-08 19:59 Marcel Holtmann
2010-07-08 22:46 ` David Miller
2010-07-08 23:28 ` Marcel Holtmann
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=cover.1278632276.git.marcel@holtmann.org \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).