]> pilppa.com Git - linux-2.6-omap-h63xx.git/commit
projects / linux-2.6-omap-h63xx.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ff2d367) | patch
[Bluetooth] Always include MTU in L2CAP config responses
authorMarcel Holtmann <marcel@holtmann.org>
Sat, 18 Nov 2006 21:15:00 +0000 (22:15 +0100)
committerDavid S. Miller <davem@sunset.davemloft.net>
Wed, 22 Nov 2006 00:16:31 +0000 (16:16 -0800)
commit820ae1b865caa05e0614004d0183ca70de2b8665
treecf93320889db023d4049ffc0123bcfb4a407982ftree | snapshot
parentff2d367ac33b9278c9516ac1888207dac11d10b0commit | diff
[Bluetooth] Always include MTU in L2CAP config responses

When sending a positive config response it shall include the actual
MTU to be used on this channel. This differs from the Bluetooth 1.1
specification where it was enough to acknowledge the config request.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
net/bluetooth/l2cap.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.