From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bug 216382 - [bisected][regression] mediatek bluetooth 13d3:3563 (mt7921e) doesn't work with audio devices.
Date: Thu, 1 Sep 2022 11:55:41 +0200 [thread overview]
Message-ID: <f39757a6-f636-39d6-81f6-3d327fcd7155@leemhuis.info> (raw)
In-Reply-To: <167d11c6-68a4-c10a-9703-fceaddac3e42@leemhuis.info>
On 24.08.22 12:19, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker speaking.
>
> I noticed a regression reported in bugzilla.kernel.org that seems to be
> handled there already, nevertheless I'd like to add to the tracking to
> ensure it's doesn't fall through the cracks in the end:
>
> #regzbot introduced: 26afbd826ee326e63a334c37fd45e82e50a61
> https://bugzilla.kernel.org/show_bug.cgi?id=216382
> #regzbot ignore-activity
Luiz, what's up with the regression?
https://bugzilla.kernel.org/show_bug.cgi?id=216382
You replied and asked for details the reporter seems to have provided
nearly two weeks ago, but it looks like nothing happened since then. Do
you still have it on your radar? Or was there any progress I just missed?
BTW, is this somehow related, as it seems to be caused by the same commit:
https://lore.kernel.org/all/5a667caf-642f-11d5-f4a4-6a73ed5742fa@eknoes.de/
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
#regzbot poke
parent reply other threads:[~2022-09-01 9:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <167d11c6-68a4-c10a-9703-fceaddac3e42@leemhuis.info>]
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=f39757a6-f636-39d6-81f6-3d327fcd7155@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).