Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: "C.D. MacEachern" <craig.daniel.maceachern@gmail.com>,
	1100928@bugs.debian.org, Kuan-Wei Chiu <visitorckw@gmail.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: Bug#1100928: [regression 6.1.y] microphone no longer records (on VivoBook_ASUSLaptop TP401MARB_J401MA)
Date: Wed, 9 Apr 2025 19:14:30 +0200	[thread overview]
Message-ID: <Z_aq9kkdswrGZRUQ@eldamar.lan> (raw)
In-Reply-To: <87zfgu1klk.wl-tiwai@suse.de>

Hi,

On Sat, Apr 05, 2025 at 09:20:23PM +0200, Takashi Iwai wrote:
> On Sat, 05 Apr 2025 16:24:45 +0200,
> Salvatore Bonaccorso wrote:
> > 
> > Control: tags -1 - moreinfo
> > 
> > On Sat, Apr 05, 2025 at 09:08:38AM -0400, C.D. MacEachern wrote:
> > > Thanks, running it now, microphone levels working fine now! Testing
> > > recording and playback, working perfectly.
> > 
> > Many thanks for testing the patch and confirming the fix.
> > 
> > Takashi, assume you will monitor that 8983dc1b66c0 ("ALSA:
> > hda/realtek: Fix built-in mic on another ASUS VivoBook model") get
> > backported to all the relevant stable series? TTBOM, it won't apply
> > cleanly to 6.1.y so Greg or Sasha might not get it down to 6.1.y
> > witout explicit backport request?
> 
> As it has Fixes tag, it'll be backported usually to stable branches,
> yes.  If it's missing, just ping stable ML.

Yes right, and in meanwhile it has made the way to 6.12.y, 6.13.y and
6.14.y. I just fear it won't go as well down to 6.1.y automatically as
the change does not apply "cleanly" so might need to make a hint :)

Thanks a lot for your work, I will apply ahead the 6.1.y inclusion the
fix as well in Debian to address https://bugs.debian.org/1100928 .

Regards,
Salvatore

      reply	other threads:[~2025-04-09 17:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <174248253267.1718.4037292692790831697.reportbug@x>
2025-03-22  7:55 ` [regression 6.1.y] microphone no longer records (on VivoBook_ASUSLaptop TP401MARB_J401MA) Salvatore Bonaccorso
2025-03-25 20:06   ` Bug#1100928: " Salvatore Bonaccorso
2025-03-25 21:02     ` Salvatore Bonaccorso
2025-03-26  6:50     ` Takashi Iwai
     [not found] ` <CAJ8x=4jNhsjw_s-p5FXBk9WScPHEdUMZ0tXnhCiya8fCf_PH7w@mail.gmail.com>
2025-03-28 23:16   ` Salvatore Bonaccorso
2025-03-29 12:06     ` Takashi Iwai
2025-04-01 18:21       ` C.D. MacEachern
2025-04-02  7:39         ` Takashi Iwai
     [not found]           ` <CAJ8x=4gN1fH6chp4C3jX1OXq2-JhbP5yUzLbqvWrAJ-u=+VNhw@mail.gmail.com>
2025-04-04  6:54             ` Takashi Iwai
2025-04-04 19:23               ` Salvatore Bonaccorso
     [not found] ` <CAJ8x=4gQQeh+yuUrBDT3P_ZkWRT+7pPujq-ZF6Fcao0V7kohFw@mail.gmail.com>
2025-04-05  6:28   ` Salvatore Bonaccorso
     [not found] ` <CAJ8x=4hmi0Afneepe15Ef-kzVZO+uyw5Row+Cooob_QR=DpwQg@mail.gmail.com>
2025-04-05 14:24   ` Salvatore Bonaccorso
2025-04-05 19:20     ` Takashi Iwai
2025-04-09 17:14       ` Salvatore Bonaccorso [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=Z_aq9kkdswrGZRUQ@eldamar.lan \
    --to=carnil@debian.org \
    --cc=1100928@bugs.debian.org \
    --cc=craig.daniel.maceachern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=tiwai@suse.de \
    --cc=visitorckw@gmail.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