From: Ville Tervo <ville.tervo@Nokia.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Resend ConfigReq on unknown options failure
Date: Wed, 28 Jul 2010 15:21:43 +0300 [thread overview]
Message-ID: <4C5020D7.7080005@nokia.com> (raw)
In-Reply-To: <20100728071631.GD22156@vigoh>
On 07/28/2010 10:16 AM, ext Gustavo F. Padovan wrote:
> Hi Ville,
>
> * Gustavo F. Padovan<gustavo@padovan.org> [2010-07-28 04:11:20 -0300]:
>
>> From: Gustavo F. Padovan<padovan@profusion.mobi>
>>
>> If the remote device send a ConfigRsp with the unknown options failure we
>> should remove that option from the ConfigReq and send it again.
>> This patch only remove the RFC option in the case it is a unknown option.
>>
>> Signed-off-by: Gustavo F. Padovan<padovan@profusion.mobi>
>> ---
>> include/net/bluetooth/l2cap.h | 17 +++++++++--------
>> net/bluetooth/l2cap.c | 28 ++++++++++++++++++++++++----
>> 2 files changed, 33 insertions(+), 12 deletions(-)
>
> Can you please test thi patch? I think it fix the unknown option
> problem.
No it didn't help. I'll try to find out why it still fails.
--
Ville
next prev parent reply other threads:[~2010-07-28 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 9:07 L2CAP unknown options Ville Tervo
2010-07-28 3:32 ` Gustavo F. Padovan
2010-07-28 7:11 ` [PATCH] Bluetooth: Resend ConfigReq on unknown options failure Gustavo F. Padovan
2010-07-28 7:16 ` Gustavo F. Padovan
2010-07-28 12:21 ` Ville Tervo [this message]
2010-07-29 18:00 ` [PATCH] Bluetooth: Don't send RFC for Basic Mode if only it is supported Gustavo F. Padovan
2010-07-29 18:04 ` Gustavo F. Padovan
2010-07-30 13:13 ` Ville Tervo
2010-07-31 22:41 ` Gustavo F. Padovan
2010-08-04 1:56 ` Marcel Holtmann
2010-08-04 6:18 ` Ville Tervo
2010-07-28 4:16 ` L2CAP unknown options Gustavo F. Padovan
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=4C5020D7.7080005@nokia.com \
--to=ville.tervo@nokia.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.