linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: johan.hedberg@gmail.com
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 0/3] Bluetooth: Various L2CAP fixes
Date: Fri, 13 Sep 2013 11:43:44 +0300	[thread overview]
Message-ID: <1379061827-8595-1-git-send-email-johan.hedberg@gmail.com> (raw)

Hi,

This patch set includes various fixes to L2CAP signaling and socket
handling.

Johan

----------------------------------------------------------------
Johan Hedberg (3):
      Bluetooth: Fix L2CAP Disconnect response for unknown CID
      Bluetooth: Fix responding to invalid L2CAP signaling commands
      Bluetooth: Fix waiting for clearing of BT_SK_SUSPEND flag

 include/net/bluetooth/bluetooth.h |  1 +
 net/bluetooth/af_bluetooth.c      | 38 +++++++++++++++++++++++++++++++++++++
 net/bluetooth/l2cap_core.c        | 10 +++++++++-
 net/bluetooth/l2cap_sock.c        |  6 ++++++
 net/bluetooth/rfcomm/sock.c       |  7 +++++--
 5 files changed, 59 insertions(+), 3 deletions(-)


             reply	other threads:[~2013-09-13  8:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13  8:43 johan.hedberg [this message]
2013-09-13  8:43 ` [PATCH 1/3] Bluetooth: Fix L2CAP Disconnect response for unknown CID johan.hedberg
2013-09-14  1:40   ` Marcel Holtmann
2013-09-14 16:11     ` Johan Hedberg
2013-09-13  8:43 ` [PATCH 2/3] Bluetooth: Fix responding to invalid L2CAP signaling commands johan.hedberg
2013-09-14  1:42   ` Marcel Holtmann
2013-09-14  5:48     ` Johan Hedberg
2013-09-13  8:43 ` [PATCH 3/3] Bluetooth: Fix waiting for clearing of BT_SK_SUSPEND flag johan.hedberg
2013-09-13 10:41   ` Anderson Lizardo
2013-09-13 11:01     ` Johan Hedberg
2013-09-14  1:43   ` Marcel Holtmann
2013-09-14  5:50     ` Johan Hedberg

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=1379061827-8595-1-git-send-email-johan.hedberg@gmail.com \
    --to=johan.hedberg@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).