kernel/net/bluetooth/a2mp.c, branch linux-4.1.y

Bluetooth: Make __next_ident function static.

2015-02-15T08:14:54Z

The __next_ident function is a local function and so do not export it and make it static. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg

Bluetooth: Make a2mp_send function static

2015-02-15T08:14:52Z

The a2mp_send function is a local function and so do not export it and make it static. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg

Bluetooth: Make amp_mgr_lookup_by_state function static

2015-02-15T08:14:51Z

The amp_mgr_lookup_by_state function does not need to be exported. So just move it to a different location and make it static. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg

Bluetooth: Make amp_mgr_list and amp_mgr_list_lock static

2015-02-15T08:14:49Z

There is no reason to have amp_mgr_list and amp_mgr_list_lock exported from a2mp.c and thus make both of them static. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg

Bluetooth: Move A2MP_FEAT_EXT declaration into A2MP source

2015-02-15T08:14:48Z

The A2MP_FEAT_EXT declaration has a single user in a2mp.c and thus just move it there. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg

first fruits - kill l2cap ->memcpy_fromiovec()

2014-12-09T21:29:10Z

Just use copy_from_iter(). That's what this method is trying to do in all cases, in a very convoluted fashion. Signed-off-by: Al Viro

put iov_iter into msghdr

2014-12-09T21:29:03Z

Note that the code _using_ ->msg_iter at that point will be very unhappy with anything other than unshifted iovec-backed iov_iter. We still need to convert users to proper primitives. Signed-off-by: Al Viro

Bluetooth: Provide L2CAP ops callback for memcpy_fromiovec

2014-07-03T15:42:43Z

The highly optimized TX path for L2CAP channels and its fragmentation within the HCI ACL packets requires to copy data from user provided IO vectors and also kernel provided memory buffers. This patch allows channel clients to provide a memcpy_fromiovec callback to keep this optimized behavior, but adapt it to kernel vs user memory for the TX path. For all kernel internal L2CAP channels, a default implementation is provided that can be referenced. In case of A2MP, this fixes a long-standing issue with wrongly accessing kernel memory as user memory. This patch originally by Marcel Holtmann. Signed-off-by: Jukka Rissanen Signed-off-by: Marcel Holtmann

Bluetooth: Use explicit header and body length for L2CAP SKB allocation

2014-07-03T15:42:42Z

When allocating the L2CAP SKB for transmission, provide the upper layers with a clear distinction on what is the header and what is the body portion of the SKB. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg

Bluetooth: Assign L2CAP socket priority when allocating SKB

2014-07-03T15:42:41Z

The SKB for L2CAP sockets are all allocated in a central callback in the socket support. Instead of having to pass around the socket priority all the time, assign it to skb->priority when actually allocating the SKB. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg