From: Bastien Nocera <hadess@hadess.net>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [PATCH v2 2/2] Bluetooth: Fix bogus check for re-auth no supported with non-ssp
Date: Thu, 30 Nov 2023 14:58:31 +0100 [thread overview]
Message-ID: <a5ae5d595ad5c97a592c66e089e396c53e764ffd.camel@hadess.net> (raw)
In-Reply-To: <CABBYNZ+TgaV5d+2N9XiqmPUvYO7zCFmNEsOh_8u4yhu9yCak+g@mail.gmail.com>
On Thu, 2023-11-30 at 08:43 -0500, Luiz Augusto von Dentz wrote:
> Hi Bastien,
>
> On Thu, Nov 30, 2023 at 7:02 AM Bastien Nocera <hadess@hadess.net>
> wrote:
> >
> > On Wed, 2020-05-20 at 14:20 -0700, Luiz Augusto von Dentz wrote:
> > > From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> > >
> > > This reverts 19f8def031bfa50c579149b200bfeeb919727b27
> > > "Bluetooth: Fix auth_complete_evt for legacy units" which seems
> > > to be
> > > working around a bug on a broken controller rather then any
> > > limitation
> > > imposed by the Bluetooth spec, in fact if there ws not possible
> > > to
> > > re-auth the command shall fail not succeed.
> > >
> > > Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> >
> > Looks like this fell through the cracks, do you want me to rebase
> > and
> > re-send it?
>
> Yeah, please resend so we get the CI to test it doesn't break
> anything.
Done.
Cheers
next prev parent reply other threads:[~2023-11-30 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 21:20 [PATCH v2 1/2] Bluetooth: Disconnect if E0 is used for Level 4 Luiz Augusto von Dentz
2020-05-20 21:20 ` [PATCH v2 2/2] Bluetooth: Fix bogus check for re-auth no supported with non-ssp Luiz Augusto von Dentz
2023-11-30 12:02 ` Bastien Nocera
2023-11-30 13:43 ` Luiz Augusto von Dentz
2023-11-30 13:58 ` Bastien Nocera [this message]
2020-06-18 17:37 ` [PATCH v2 1/2] Bluetooth: Disconnect if E0 is used for Level 4 Luiz Augusto von Dentz
2020-06-19 7:54 ` 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=a5ae5d595ad5c97a592c66e089e396c53e764ffd.camel@hadess.net \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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).