From: coldolt <andypalmadi@gmail.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "An, Tedd" <tedd.an@intel.com>,
"kai.heng.feng@canonical.com" <kai.heng.feng@canonical.com>,
"marcel@holtmann.org" <marcel@holtmann.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] Bluetooth not working on 5.15+ since "Bluetooth: Move shutdown callback before flushing tx and rx queue"
Date: Sun, 23 Jan 2022 22:11:19 +0200 [thread overview]
Message-ID: <CAJvGw+CKz_tZXKkuzrPURLJsh1JBkO1ge7V_owa0htk9pEJsZw@mail.gmail.com> (raw)
In-Reply-To: <7672718f-b34e-225d-ff53-1199026728b7@leemhuis.info>
On Sun, Jan 23, 2022 at 11:28 AM Thorsten Leemhuis
<regressions@leemhuis.info> wrote:
>
> Top-posting for once, to make this easy accessible to everyone.
>
> Coldolt, could you please check if this regression is still in 5.17-rc1
> or 5.16.2? I wonder if this patch fixed things:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.16.y&id=8e8cae520210139aab4b701a822bbefb13b8f007
>
> Ciao, Thorsten
Yes, that commit fixes it for me. This same issue seems to have come
up many times in the past months, it is a duplicate of
#regzbot dup-of:
https://lore.kernel.org/lkml/b0f6f66b-28aa-9d43-0aab-e6887ee0fda8@logobject.ch/
#regzbot dup-of:
https://lore.kernel.org/lkml/20211202162256.31837-1-tiwai@suse.de/
#regzbot fixed-by: 95655456e7ce
prev parent reply other threads:[~2022-01-23 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 23:36 [REGRESSION] Bluetooth not working on 5.15+ since "Bluetooth: Move shutdown callback before flushing tx and rx queue" coldolt
2021-12-10 1:10 ` An, Tedd
2021-12-10 9:16 ` Thorsten Leemhuis
2022-01-20 13:08 ` Thorsten Leemhuis
2022-01-23 9:28 ` Thorsten Leemhuis
2022-01-23 20:11 ` coldolt [this message]
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=CAJvGw+CKz_tZXKkuzrPURLJsh1JBkO1ge7V_owa0htk9pEJsZw@mail.gmail.com \
--to=andypalmadi@gmail.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=tedd.an@intel.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).