From: Gustavo Padovan <padovan@profusion.mobi>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: pull request: bluetooth 2011-12-19
Date: Mon, 19 Dec 2011 11:35:24 -0200 [thread overview]
Message-ID: <20111219133524.GB2610@joana> (raw)
Hi John,
3 fixes for 3.2! There one revert that was causing connection issues, a RFCOMM
fix to a potential kernel panic, and the last on L2CAP to a possible access to
uninitialized data due to broken remote devices.
Please pull, or let me know any problems.
Gustavo
The following changes since commit 78feb35b8161acd95c33a703ed6ab6f554d29387:
iwlwifi: allow to switch to HT40 if not associated (2011-12-14 13:56:55 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth master
Gustavo F. Padovan (1):
Revert "Bluetooth: Revert: Fix L2CAP connection establishment"
Mat Martineau (2):
Bluetooth: Prevent uninitialized data access in L2CAP configuration
Bluetooth: Clear RFCOMM session timer when disconnecting last channel
net/bluetooth/hci_conn.c | 2 +-
net/bluetooth/l2cap_core.c | 12 +++++++++++-
net/bluetooth/rfcomm/core.c | 1 +
3 files changed, 13 insertions(+), 2 deletions(-)
reply other threads:[~2011-12-19 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111219133524.GB2610@joana \
--to=padovan@profusion.mobi \
--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