From: Marcel Holtmann <marcel@holtmann.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Pull request: bluetooth-2.6 2009-11-16
Date: Mon, 16 Nov 2009 01:48:20 +0100 [thread overview]
Message-ID: <cover.1258331614.git.marcel@holtmann.org> (raw)
Hi Dave,
here are three additional patches that should go into 2.6.32 before its
final release.
The first one fixes a regression with Secure Simple Pairing support. I
had that patch for a while, but it took some time to verify that it
doesn't break the Bluetooth qualification. The Bluetooth 2.1 GAP testing
is a major pain and always surprises you.
The second and third patches are fixing two regression from the L2CAP
ERTM support. When ERTM is not supported or not configured we have to
use Basic Mode and really stick to it. Other Bluetooth stacks are not
capable of handling unknown options properly.
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 | 1 +
net/bluetooth/l2cap.c | 13 +++++++++----
2 files changed, 10 insertions(+), 4 deletions(-)
through these ChangeSets:
Andrei Emeltchenko (1):
Bluetooth: Set general bonding security for ACL by default
Gustavo F. Padovan (2):
Bluetooth: Select Basic Mode as default for SOCK_SEQPACKET
Bluetooth: Fix regression with L2CAP configuration in Basic Mode
next reply other threads:[~2009-11-16 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 0:48 Marcel Holtmann [this message]
2009-11-16 0:48 ` [PATCH 1/3] Bluetooth: Set general bonding security for ACL by default Marcel Holtmann
2009-11-16 0:48 ` [PATCH 2/3] Bluetooth: Select Basic Mode as default for SOCK_SEQPACKET Marcel Holtmann
2009-11-16 0:48 ` [PATCH 3/3] Bluetooth: Fix regression with L2CAP configuration in Basic Mode Marcel Holtmann
2009-11-16 5:01 ` Pull request: bluetooth-2.6 2009-11-16 David Miller
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.1258331614.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).