This patch set adds support for handling extended headers of bnep control frames which is mandatory. Until now extended headers for control messages was ignored. Patch [1/4] adds setting of err variable if control message is not understood. Patch [2/4] adds additional ioctl for get supported bnep features. This is needed for user space to know if handling of sending success setup response frame should be handled by kernel or by user space. Patch [3/4] adds support for handling extended headers of bnep control frames. Patch [4/4] adds support for handling connection setup request. Patch set tested with PTS bnep test cases. No regression, issues found during testing. v2. - Added ioctl definition to compat_ioctl, - Distinct bnep session flags and bnep features. v3. - Splited extended header, connection setup request handling into separated patches, - Fixed flags, supported features defines as Marcel pointed, - Extended commit messages, - Remove copying flags from us to kernel bnep session, - Fix setting bnep session bits as Marcel pointed. v4. - Unify internal/us flags usage like in HIDP, CMTP, - Refactor send setup response as Marcel suggested, - Make supported feature variable as local ioctl variable and set it while adding session if required. v5. - Rebase on top of "flags validation check" patch set, - Remove blank line style fix, - Add session flag setting after validation flag check. Grzegorz Kolodziejczyk (4): Bluetooth: bnep: Return err value while sending cmd is not understood Bluetooth: bnep: Add support for get bnep features via ioctl Bluetooth: bnep: Add support to extended headers of control frames Bluetooth: bnep: Handle BNEP connection setup request fs/compat_ioctl.c | 1 + net/bluetooth/bnep/bnep.h | 4 +++ net/bluetooth/bnep/core.c | 64 ++++++++++++++++++++++++++++++++++++----------- net/bluetooth/bnep/sock.c | 7 ++++++ 4 files changed, 62 insertions(+), 14 deletions(-) -- 2.1.0 -- 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
