regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (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: [regression] Bug 217063 - Commit 2232b2d breaks microphone on Lenovo "82SJ" Ideapad 14ARH7
Date: Tue, 21 Feb 2023 13:44:28 +0100	[thread overview]
Message-ID: <698e7bfa-09dc-ad74-3eba-ceacd7a29f18@leemhuis.info> (raw)

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 :

> [reply] [−] Description Joseph R 2023-02-21 00:35:34 UTC
> 
> Created attachment 303765 [details] lspci -vv
> 
> Commit 2232b2dd8cd4f1e6d554b2c3f6899ce36f791b67, intended to fix
> sound on Lenovo Yoga Slim 7 Pro X, makes the microphone on Lenovo
> Ideapad 14 14ARH7 with product code Lenovo "82SJ" unusable.
> 
> Simply removing the lines added by the commit make the microphone
> work again without issues.
> 
> Attached is lspci on a kernel with the lines removed.
> 
> First kernel bug report, so please let me know how I can help get
> this fixed!


See the ticket for more details.


[TLDR for the rest of this mail: I'm adding this report to the list of
tracked Linux kernel regressions; the text you find below is based on a
few templates paragraphs you might have encountered already in similar
form.]

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: 2232b2dd8cd4f1e6d5
https://bugzilla.kernel.org/show_bug.cgi?id=217063
#regzbot title: alsa/asoc: microphone on Lenovo "82SJ" Ideapad 14ARH7 broken
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (e.g. the buzgzilla ticket and maybe this mail as well, if
this thread sees some discussion). See page linked in footer for details.

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
If I did something stupid, please tell me, as explained on that page.

             reply	other threads:[~2023-02-21 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 12:44 Linux regression tracking (Thorsten Leemhuis) [this message]
2023-03-16  9:36 ` [regression] Bug 217063 - Commit 2232b2d breaks microphone on Lenovo "82SJ" Ideapad 14ARH7 Linux regression tracking #update (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=698e7bfa-09dc-ad74-3eba-ceacd7a29f18@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).