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-next 2011-10-03
Date: Mon, 3 Oct 2011 23:28:21 -0300 [thread overview]
Message-ID: <20111004022821.GA7951@joana> (raw)
Hi John,
Last pull request for 3.2, just a few patches here. The most important ones are
from Mat Martineau that adds support to handle fragmented skbs in
bt_sock_stream_recvmsg(). The rest are just fixes and clean ups.
Please pull! Or let me know any problem, thanks.
Gustavo
The following changes since commit 76ed94be65c8bd80b565865c186dd9f24bb2f23b:
ath9k_hw: set pci_express capability true for AR9480 (2011-10-03 15:22:42 -0400)
are available in the git repository at:
git://github.com/padovan/bluetooth-next.git master
Anderson Lizardo (1):
Bluetooth: use recommended LE connection parameters
Andre Guedes (1):
Bluetooth: hci_le_adv_report_evt code refactoring
Mat Martineau (3):
Bluetooth: Linearize skbs for use in BNEP, CMTP, HIDP, and RFCOMM
Bluetooth: Handle fragmented skbs in bt_sock_stream_recvmsg()
Bluetooth: Perform L2CAP SDU reassembly without copying data
Oliver Neukum (1):
btusb: add device entry for Broadcom SoftSailing
Peter Hurley (1):
Bluetooth: Allow ACL packets over USB in HCI_RAW mode
Szymon Janc (1):
Bluetooth: Mark not declared l2cap_core functions as static
Waldemar Rymarkiewicz (1):
Bluetooth: Fix possible NULL pointer dereference
drivers/bluetooth/btusb.c | 6 +-
include/net/bluetooth/l2cap.h | 3 +-
net/bluetooth/af_bluetooth.c | 30 +++++-
net/bluetooth/bnep/core.c | 5 +-
net/bluetooth/cmtp/core.c | 5 +-
net/bluetooth/hci_conn.c | 14 +-
net/bluetooth/hci_event.c | 20 ++--
net/bluetooth/hidp/core.c | 10 ++-
net/bluetooth/l2cap_core.c | 255 ++++++++++++++---------------------------
net/bluetooth/rfcomm/core.c | 5 +-
10 files changed, 157 insertions(+), 196 deletions(-)
reply other threads:[~2011-10-04 2:27 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=20111004022821.GA7951@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;
as well as URLs for NNTP newsgroup(s).