From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Mark Brown <broonie@kernel.org>,
Joseph R <prosenfeld@Yuhsbstudents.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org,
Linux kernel regressions list <regressions@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [regression] Bug 217063 - Commit 2232b2d breaks microphone on Lenovo "82SJ" Ideapad 14ARH7
Date: Thu, 16 Mar 2023 10:36:51 +0100 [thread overview]
Message-ID: <cf688390-8b70-1367-eb8e-48a2fee1a1d5@leemhuis.info> (raw)
In-Reply-To: <698e7bfa-09dc-ad74-3eba-ceacd7a29f18@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 21.02.23 13:44, Linux regression tracking (Thorsten Leemhuis) wrote:
> Hi, this is your Linux kernel regression tracker.
>
> I noticed a regression report in bugzilla.kernel.org. As many (most?)
> kernel developer don't keep an eye on it, I decided to forward it by
> mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217063 :
#regzbot resolve: no longer happens with the latest kernels
#regzbot ignore-activity
For details see https://bugzilla.kernel.org/show_bug.cgi?id=217063#c4
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-03-16 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 12:44 [regression] Bug 217063 - Commit 2232b2d breaks microphone on Lenovo "82SJ" Ideapad 14ARH7 Linux regression tracking (Thorsten Leemhuis)
2023-03-16 9:36 ` Linux regression tracking #update (Thorsten Leemhuis) [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=cf688390-8b70-1367-eb8e-48a2fee1a1d5@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perex@perex.cz \
--cc=prosenfeld@Yuhsbstudents.org \
--cc=regressions@lists.linux.dev \
--cc=tiwai@suse.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).