Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <SJ0PR13MB575532A88E75738299CB1636FEB49@SJ0PR13MB5755.namprd13.prod.outlook.com>
 <0b943515-915b-8bdd-2e60-a6f38e0db17a@eknoes.de>
In-Reply-To: <0b943515-915b-8bdd-2e60-a6f38e0db17a@eknoes.de>
From:   Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date:   Thu, 7 Jul 2022 13:26:49 -0700
Message-ID: <CABBYNZKVQKT2GD7hCei+1r08d5PoFjD8U76G=nLrGw4wQFCGuw@mail.gmail.com>
Subject: Re: Linux v5.4.199: Bluetooth: hci_event: Ignore multiple conn
 complete events
To:     =?UTF-8?Q?S=C3=B6nke_Huster?= <soenke.huster@eknoes.de>
Cc:     John Klug <John.Klug@multitech.com>,
        Linux-Bluetooth MailingList <linux-bluetooth@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi John,

On Tue, Jun 28, 2022 at 11:35 PM S=C3=B6nke Huster <soenke.huster@eknoes.de=
> wrote:
>
> Hi John,
>
> On 25.06.22 00:46, John Klug wrote:
> > This patch updated for the 5.4.199 kernel on Friday, 24 June 2022 by
> > John Klug <john.klug@multitech.com>
>
> Thanks for backporting! I do not know how the process is for backporting =
patches to stable releases - do you need my Tested-by or Reviewed-by or sim=
ilar? I'll test it in the afternoon.
>
> Furthermore, I think it must go to stable, and there seem to be some guid=
ance how that works over here:
> https://www.kernel.org/doc/html/v4.17/process/stable-kernel-rules.html#op=
tion-3

This probably should be sent to stable tree directly, at least our CI
won't be able to test it as it expects to be applied to
bluetooth-next.

--=20
Luiz Augusto von Dentz