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;
Message-ID: <7afb6b94-cbd8-fecd-9c68-4200d87cda59@leemhuis.info>
Date:   Sun, 10 Apr 2022 11:05:46 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.7.0
Subject: Re: [PATCH v4 1/4] Bluetooth: HCI: Add
 HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN quirk
Content-Language: en-US
To:     patchwork-bot+bluetooth@kernel.org,
        Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc:     linux-bluetooth@vger.kernel.org,
        Marcel Holtmann <marcel@holtmann.org>,
        Jakub Kicinski <kuba@kernel.org>
References: <20220401233826.122544-1-luiz.dentz@gmail.com>
 <164917981297.18365.2641777452049475210.git-patchwork-notify@kernel.org>
From:   Thorsten Leemhuis <regressions@leemhuis.info>
In-Reply-To: <164917981297.18365.2641777452049475210.git-patchwork-notify@kernel.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi, this is your Linux kernel regression tracker.

On 05.04.22 19:30, patchwork-bot+bluetooth@kernel.org wrote:
> 
> This series was applied to bluetooth/bluetooth-next.git (master)
> by Marcel Holtmann <marcel@holtmann.org>:
> 
> On Fri,  1 Apr 2022 16:38:23 -0700 you wrote:
>> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

BTW: Thx for taking care of this, Luiz!

>> This adds HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN quirk which can be
>> used to mark HCI_Enhanced_Setup_Synchronous_Connection as broken even
>> if its support command bit are set since some controller report it as
>> supported but the command don't work properly with some configurations
>> (e.g. BT_VOICE_TRANSPARENT/mSBC).
>>
>> [...]
> 
> Here is the summary with links:
>   - [v4,1/4] Bluetooth: HCI: Add HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN quirk
>     https://git.kernel.org/bluetooth/bluetooth-next/c/c625b467f47c
>   - [v4,2/4] Bluetooth: Print broken quirks
>     https://git.kernel.org/bluetooth/bluetooth-next/c/fa5cd0fd5bdf
>   - [v4,3/4] Bluetooth: btusb: Set HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN for QCA
>     https://git.kernel.org/bluetooth/bluetooth-next/c/38a1944deda4
>   - [v4,4/4] Bluetooth: hci_sync: Split hci_dev_open_sync
>     (no matching commit)
> 
> You are awesome, thank you!

Hey, this patchset is fixing a regression from 5.16 (see patch 3/4), but
apparently is only scheduled to go upstream in the next cycle, as it was
applied to bluetooth-next.git. The patches also seem to miss tags to get
them backported to stable. Is that intentional? At least patches 1, 2,
and 3 don't look that complex, why can't they get in this cycle and get
backported to stable soon to finally provide a solution for users that
are plagued by this for weeks already?

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.