From: Marcel Holtmann <marcel@holtmann.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Pull request: bluetooth-next-2.6 2010-08-04
Date: Wed, 4 Aug 2010 13:38:14 -0700 [thread overview]
Message-ID: <cover.1280932089.git.marcel@holtmann.org> (raw)
Hi John,
I have four more bug fixes for the 2.6.36 merge window. All of them
are pretty straight forward.
They are still based on your wireless-next-2.6 tree. I hope that is
no problem for you. I can rebase them quickly if needed.
Regards
Marcel
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-next-2.6.git master
This will update the following files:
include/net/bluetooth/hci_core.h | 2 +-
net/bluetooth/hci_core.c | 2 +-
net/bluetooth/hci_sock.c | 8 +++-----
net/bluetooth/hci_sysfs.c | 3 +--
net/bluetooth/l2cap.c | 24 +++++++++++++++++++++---
net/bluetooth/rfcomm/tty.c | 2 +-
6 files changed, 28 insertions(+), 13 deletions(-)
through these ChangeSets:
David Miller (1):
Bluetooth: Use list_head for HCI blacklist head
Gustavo F. Padovan (2):
Bluetooth: Remove __exit from rfcomm_cleanup_ttys()
Bluetooth: Don't send RFC for Basic Mode if only it is supported
Ville Tervo (1):
Bluetooth: Check result code of L2CAP information response
reply other threads:[~2010-08-04 20:38 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=cover.1280932089.git.marcel@holtmann.org \
--to=marcel@holtmann.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).