From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Chris Clayton <chris2553@googlemail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Bluetooth <linux-bluetooth@vger.kernel.org>,
regressions@lists.linux.dev
Subject: Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
Date: Thu, 24 Feb 2022 17:18:02 +0100 [thread overview]
Message-ID: <a0ec4d70-35d7-ab32-4561-df77bcc6d0fd@leemhuis.info> (raw)
In-Reply-To: <CABBYNZ+cL4f8xvTJFQGLgqPueE=-UsOtvcPQez0BEsJ5xGppfQ@mail.gmail.com>
On 24.02.22 16:16, Luiz Augusto von Dentz wrote:
> On Thu, Feb 24, 2022 at 2:08 AM Chris Clayton <chris2553@googlemail.com> wrote:
>> On 24/02/2022 08:16, Luiz Augusto von Dentz wrote:
>>> On Wed, Feb 23, 2022 at 9:59 PM Chris Clayton <chris2553@googlemail.com> wrote:
>>>> On 23/02/2022 22:42, Chris Clayton wrote:
> [...]
>> In the meantime I've copied this email to regressions@lists.linux.dev, so they can track this.
Many thx for this, much appreciated.
> Hmm, is that really necessary? 5.17 has not been release tagged yet
> and you are already considering it a regression?
Sure it's a regression, just one that didn't make it into a release yet.
But tracking regressions in mainline is just as important as tracking
them in stable trees, as it allows Linus to take a look at the known
regressions when he needs to decide between "release another rc" and
"call this finished and release the final". That's why mainline in the
past often was the main focus of regression tracking or the only tree
for which is was performed!
> [...]
Ciao, Thorsten
next prev parent reply other threads:[~2022-02-24 17:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 1:44 bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices Chris Murphy
2022-02-15 15:29 ` Chris Murphy
2022-02-15 15:38 ` Chris Murphy
2022-02-16 3:47 ` Chris Murphy
2022-02-16 23:49 ` Luiz Augusto von Dentz
2022-02-17 1:35 ` Chris Murphy
2022-02-17 23:36 ` Chris Murphy
2022-02-18 0:15 ` Luiz Augusto von Dentz
2022-02-18 3:49 ` Chris Murphy
2022-02-21 11:39 ` Chris Clayton
2022-02-21 13:22 ` Chris Clayton
2022-02-21 17:11 ` Luiz Augusto von Dentz
2022-02-21 20:23 ` Chris Clayton
2022-02-21 21:27 ` Luiz Augusto von Dentz
2022-02-21 22:33 ` Chris Clayton
2022-02-22 20:03 ` Chris Clayton
2022-02-23 17:51 ` Luiz Augusto von Dentz
2022-02-23 22:42 ` Chris Clayton
2022-02-24 5:59 ` Chris Clayton
2022-02-24 8:16 ` Luiz Augusto von Dentz
2022-02-24 10:08 ` Chris Clayton
2022-02-24 15:16 ` Luiz Augusto von Dentz
2022-02-24 16:18 ` Thorsten Leemhuis [this message]
2022-02-26 8:04 ` Chris Clayton
2022-02-28 19:34 ` Luiz Augusto von Dentz
2022-02-28 21:02 ` Chris Clayton
2022-02-28 21:20 ` Luiz Augusto von Dentz
2022-03-01 9:26 ` Chris Clayton
2022-03-01 18:34 ` Luiz Augusto von Dentz
2022-03-01 18:56 ` Chris Clayton
2022-03-01 18:57 ` Luiz Augusto von Dentz
2022-03-01 19:40 ` Chris Clayton
2022-03-01 22:40 ` Luiz Augusto von Dentz
2022-03-01 22:47 ` Luiz Augusto von Dentz
2022-03-02 2:31 ` Luiz Augusto von Dentz
2022-03-02 6:55 ` Luiz Augusto von Dentz
2022-03-02 9:59 ` Chris Clayton
2022-03-02 8:54 ` Chris Clayton
2022-02-24 8:24 ` Chris Clayton
2022-02-21 17:12 ` Luiz Augusto von Dentz
2022-02-21 17:18 ` Luiz Augusto von Dentz
2022-02-24 10:26 ` Thorsten Leemhuis
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=a0ec4d70-35d7-ab32-4561-df77bcc6d0fd@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=chris2553@googlemail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=luiz.dentz@gmail.com \
--cc=regressions@lists.linux.dev \
/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).