All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Kolodziejczyk <grzegorz.kolodziejczyk@tieto.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v4 0/4] Handling extended headers of bnep control frames
Date: Wed,  1 Apr 2015 16:24:11 +0200	[thread overview]
Message-ID: <1427898255-27496-1-git-send-email-grzegorz.kolodziejczyk@tieto.com> (raw)

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.

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 | 58 +++++++++++++++++++++++++++++++++++++----------
 net/bluetooth/bnep/sock.c |  8 +++++++
 4 files changed, 59 insertions(+), 12 deletions(-)

-- 
2.1.0


             reply	other threads:[~2015-04-01 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 14:24 Grzegorz Kolodziejczyk [this message]
2015-04-01 14:24 ` [PATCH v4 1/4] Bluetooth: bnep: Return err value while sending cmd is not understood Grzegorz Kolodziejczyk
2015-04-01 14:24 ` [PATCH v4 2/4] Bluetooth: bnep: Add support for get bnep features via ioctl Grzegorz Kolodziejczyk
2015-04-01 20:26   ` Marcel Holtmann
2015-04-02  8:09     ` Grzegorz Kolodziejczyk
2015-04-01 14:24 ` [PATCH v4 3/4] Bluetooth: bnep: Add support to extended headers of control frames Grzegorz Kolodziejczyk
2015-04-01 14:24 ` [PATCH v4 4/4] Bluetooth: bnep: Handle BNEP connection setup request Grzegorz Kolodziejczyk
2015-04-01 20:28   ` Marcel Holtmann
2015-04-02  8:40     ` Grzegorz Kolodziejczyk

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=1427898255-27496-1-git-send-email-grzegorz.kolodziejczyk@tieto.com \
    --to=grzegorz.kolodziejczyk@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.