From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: pull request: bluetooth-next-2.6 2011-02-08
Date: Tue, 8 Feb 2011 15:29:06 -0200 [thread overview]
Message-ID: <20110208172905.GA2160@joana> (raw)
Hi John,
That is a big one. The major things here are the HCI management interface and
the l2cap.c file split. On the HCI management interface Johan Hedberg took a
big step implement support for many HCI commandsi/events in kernel side.
I did the l2cap.c split, that file was almost 5000 lines big a more code is
expected to come soon.
The rest are only bug fixes, expect a patch from Andrei Emeltchenko to add
support to configure the flushable flag in LMP.
Please pull. Thanks.
The following changes since commit 3ad97fbcc233a295f2ccc2c6bdeb32323e360a5e:
mac80211: remove unneeded check (2011-02-07 16:18:28 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next-2.6.git master
Andrei Emeltchenko (3):
Bluetooth: Use non-flushable by default L2CAP data packets
Bluetooth: Do not use assignments in IF conditions
Bluetooth: fix crash by disabling tasklet in sock accept
Bao Liang (1):
Bluetooth: Set conn state to BT_DISCONN to avoid multiple responses
Cho, Yu-Chen (1):
Bluetooth: add Atheros BT AR9285 fw supported
Gustavo F. Padovan (19):
Merge branch 'master' of git://git.kernel.org/.../padovan/bluetooth-2.6 into wireless
Bluetooth: Fix setting of MTU for ERTM and Streaming Mode
Bluetooth: Rename l2cap.c to l2cap_core.c
Bluetooth: Initial work for L2CAP split.
Bluetooth: move l2cap_sock_ops to l2cap_sock.c
Bluetooth: move l2cap_sock_release() to l2cap_sock.c
Bluetooth: move l2cap_sock_bind()/listen() to l2cap_sock.c
Bluetooth: move l2cap_sock_accept() to l2cap_sock.c
Bluetooth: move l2cap_sock_getname() to l2cap_sock.c
Bluetooth: move l2cap_sock_setsockopt() to l2cap_sock.c
Bluetooth: move l2cap_sock_getsockopt() to l2cap_sock.c
Bluetooth: move l2cap_sock_connect() to l2cap_sock.c
Bluetooth: move l2cap_sock_recvmsg() to l2cap_sock.c
Bluetooth: move l2cap_sock_shutdown() to l2cap_sock.c
Bluetooth: move l2cap_sock_sendmsg() to l2cap_sock.c
Bluetooth: move L2CAP sock timers function to l2cap_sock.c
Bluetooth: move l2cap_sock_kill() to l2cap_sock.c
Bluetooth: move __l2cap_sock_close() to l2cap_sock.c
Bluetooth: update Bluetooth daemon name in Kconfig help
Jesper Juhl (1):
Bluetooth: Fix failure to release lock in read_index_list()
Johan Hedberg (25):
Bluetooth: Implement automatic setup procedure for local adapters
Bluetooth: Add support for management powered event
Bluetooth: Add support for set_powered management command
Bluetooth: Add support for set_discoverable management command
Bluetooth: Add set_connectable management command
Bluetooth: Unify mode related management messages to a single struct
Bluetooth: Add flag to track managment controlled adapters
Bluetooth: Add send_mode_rsp convenience function for mgmt.c
Bluetooth: Implement set_pairable managment command
Bluetooth: Implement UUID handling through the management interface
Bluetooth: Implement debugfs support for listing UUIDs
Bluetooth: Reject pairing requests when in non-pairable mode
Bluetooth: Add special handling with __hci_request and HCI_INIT
Bluetooth: Add controller side link key clearing to hci_init_req
Bluetooth: Remove page timeout setting from HCI init sequence
Bluetooth: Implement a more complete adapter initialization sequence
Bluetooth: Add class of device control to the management interface
Bluetooth: Implement link key handling for the management interface
Bluetooth: Add connected/disconnected management events
Bluetooth: Add disconnect managment command
Bluetooth: Add support for connect failed management event
Bluetooth: Add get_connections managment interface command
Bluetooth: Create common cmd_complete function for mgmt.c
Bluetooth: Add support for PIN code handling in the management interface
Bluetooth: Add set_io_capability management command
Rogério Brito (1):
Bluetooth: ath3k: Avoid duplication of code
drivers/bluetooth/ath3k.c | 10 +-
drivers/bluetooth/btusb.c | 3 +
include/net/bluetooth/bluetooth.h | 5 +
include/net/bluetooth/hci.h | 57 ++
include/net/bluetooth/hci_core.h | 62 ++-
include/net/bluetooth/l2cap.h | 32 +
include/net/bluetooth/mgmt.h | 142 +++
net/bluetooth/Kconfig | 6 +-
net/bluetooth/Makefile | 1 +
net/bluetooth/af_bluetooth.c | 19 +-
net/bluetooth/cmtp/capi.c | 3 +-
net/bluetooth/cmtp/core.c | 9 +-
net/bluetooth/hci_conn.c | 1 +
net/bluetooth/hci_core.c | 230 ++++-
net/bluetooth/hci_event.c | 457 +++++++++-
net/bluetooth/hci_sock.c | 6 +-
net/bluetooth/hci_sysfs.c | 52 +
net/bluetooth/hidp/core.c | 9 +-
net/bluetooth/{l2cap.c => l2cap_core.c} | 1618 ++++++-------------------------
net/bluetooth/l2cap_sock.c | 1150 ++++++++++++++++++++++
net/bluetooth/mgmt.c | 1310 +++++++++++++++++++++++---
21 files changed, 3668 insertions(+), 1514 deletions(-)
rename net/bluetooth/{l2cap.c => l2cap_core.c} (78%)
create mode 100644 net/bluetooth/l2cap_sock.c
--
Gustavo F. Padovan
http://profusion.mobi
reply other threads:[~2011-02-08 17:28 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=20110208172905.GA2160@joana \
--to=padovan@profusion.mobi \
--cc=linux-bluetooth@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).