linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kandukuri Vikram <vkandukuri@atheros.com>
To: <marcel@holtmann.org>
Cc: <linux-bluetooth@vger.kernel.org>, <vikram.kandukuri@gmail.com>
Subject: [PATCH] According to BNEP test spec proper response should be sent for a setup connection request message after the BNEP connection setup has been completed
Date: Thu, 3 Dec 2009 15:12:51 +0530	[thread overview]
Message-ID: <20091203094250.GC7602@atheros-laptop> (raw)


 Signed-off-by: Vikram Kandukuri <Vikram.Kandukuri@atheors.com>
---
 net/bluetooth/bnep/core.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/net/bluetooth/bnep/core.c b/net/bluetooth/bnep/core.c
index cafe9f5..29b1b22 100644
--- a/net/bluetooth/bnep/core.c
+++ b/net/bluetooth/bnep/core.c
@@ -230,7 +230,6 @@ static int bnep_rx_control(struct bnep_session *s, void *data, int len)
 
 	switch (cmd) {
 	case BNEP_CMD_NOT_UNDERSTOOD:
-	case BNEP_SETUP_CONN_REQ:
 	case BNEP_SETUP_CONN_RSP:
 	case BNEP_FILTER_NET_TYPE_RSP:
 	case BNEP_FILTER_MULTI_ADDR_RSP:
@@ -245,6 +244,10 @@ static int bnep_rx_control(struct bnep_session *s, void *data, int len)
 		err = bnep_ctrl_set_mcfilter(s, data, len);
 		break;
 
+	case BNEP_SETUP_CONN_REQ:
+		err = bnep_send_rsp(s, BNEP_SETUP_CONN_RSP, BNEP_CONN_NOT_ALLOWED);
+		break;
+
 	default: {
 			u8 pkt[3];
 			pkt[0] = BNEP_CONTROL;
-- 
1.6.0.4

             reply	other threads:[~2009-12-03  9:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03  9:42 Kandukuri Vikram [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-04  6:37 [PATCH] According to BNEP test spec proper response should be sent for a setup connection request message after the BNEP connection setup has been completed Kandukuri Vikram

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=20091203094250.GC7602@atheros-laptop \
    --to=vkandukuri@atheros.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=vikram.kandukuri@gmail.com \
    /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).