Hi Johan, > Since we're not at the moment applying anything new to bluetooth-next > (due to the merge window being still open) I'm sending all my pending > patches in a single set to ease applying them in the correct order. > > The two patches requiring some special consideration for 3.17 and stable > kernel trees are the following two: > > Bluetooth: Fix incorrect LE CoC PDU length restriction based on HCI MTU > Bluetooth: Fix hci_conn reference counting for auto-connections > > Of those two the second one is a "must have" for 3.17 whereas the first > one would be nice to get fixed for older kernels. All other patches in > this set are fine to wait for 3.18. > > Johan > > ---------------------------------------------------------------- > Johan Hedberg (9): > Bluetooth: Fix incorrect LE CoC PDU length restriction based on HCI MTU > Bluetooth: Remove unnecessary l2cap_chan_unlock before l2cap_chan_add > Bluetooth: Fix hci_conn reference counting for fixed channels > Bluetooth: Fix hci_conn reference counting for auto-connections > Bluetooth: Set addr_type only when it's needed > Bluetooth: Optimize connection parameter lookup for LE connections > Bluetooth: Improve *_get() functions to return the object type > Bluetooth: Fix using hci_conn_get() for hci_conn pointers > Bluetooth: Refactor connection parameter freeing into its own function > > include/net/bluetooth/hci_core.h | 5 ++++- > include/net/bluetooth/l2cap.h | 3 ++- > net/bluetooth/hci_conn.c | 9 +++++++++ > net/bluetooth/hci_core.c | 33 +++++++++++++++++++++++---------- > net/bluetooth/hci_event.c | 31 +++++++++++++++++++++++-------- > net/bluetooth/hidp/core.c | 10 ++++------ > net/bluetooth/l2cap_core.c | 26 ++++++++++++++------------ > net/bluetooth/l2cap_sock.c | 8 ++++++++ > net/bluetooth/mgmt.c | 10 +++++++--- > 9 files changed, 94 insertions(+), 41 deletions(-) all 9 patches have been applied to bluetooth-next tree. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
