From: Bastien Nocera <hadess@hadess.net>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Florian Dollinger <dollinger.florian@gmx.de>
Subject: Re: [PATCH] Bluetooth: L2CAP: Try harder to accept device not knowing options
Date: Wed, 06 Jan 2021 10:25:55 +0100 [thread overview]
Message-ID: <ebbb9f334f6f0cecdb46ddce63483df165ea12ec.camel@hadess.net> (raw)
In-Reply-To: <6e6d72ff9aa14a65d6d0df5bd68a6ad6887f31c2.camel@hadess.net>
On Wed, 2020-12-16 at 16:49 +0100, Bastien Nocera wrote:
> <snip>
> The tests fail for me in the same on a kernel with and without
> the
> patch:
> - Expected that the IUT transmits an L2CAP_ConfigRsp includes the
> unsupported option that Lower Tester sent.
> Final Verdict:FAIL
> L2CAP/COS/CFD/BV-14-C finished
>
> Is this expected? I was using an 5.10-rc7 kernel with and without the
> patch I sent. I can send you the full results off-list if you want
> them.
Any news on that? Is the error expected, should I test with a newer
version of the kernel? I'd really like to finally land this...
next prev parent reply other threads:[~2021-01-06 9:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 17:29 [PATCH] Bluetooth: L2CAP: Try harder to accept device not knowing options Bastien Nocera
2020-12-08 18:05 ` bluez.test.bot
[not found] ` <CABBYNZJNTDek+kKS5wtrr67Xx8DmFGvcV13cLSxULgJRa5N+3g@mail.gmail.com>
2020-12-08 18:27 ` [PATCH] " Bastien Nocera
2020-12-08 18:48 ` Luiz Augusto von Dentz
2020-12-16 15:49 ` Bastien Nocera
2021-01-06 9:25 ` Bastien Nocera [this message]
2021-01-06 9:47 ` Archie Pusaka
2021-01-06 10:36 ` Bastien Nocera
2021-01-06 16:42 ` Bastien Nocera
2021-01-08 1:29 ` Luiz Augusto von Dentz
2021-01-13 12:32 ` Bastien Nocera
2021-01-25 18:29 ` Bastien Nocera
2021-01-25 18:31 ` Bastien Nocera
2021-01-25 18:29 ` Marcel Holtmann
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=ebbb9f334f6f0cecdb46ddce63483df165ea12ec.camel@hadess.net \
--to=hadess@hadess.net \
--cc=dollinger.florian@gmx.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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).