From: Takashi Iwai <tiwai@suse.de>
To: phasta@kernel.org, Philipp Stanner <phasta@mailbox.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Alok Tiwari <alok.a.tiwari@oracle.com>,
perex@perex.cz, tiwai@suse.com,
andriy.shevchenko@linux.intel.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: intel8x0: Fix incorrect codec index usage in mixer for ICH4
Date: Mon, 23 Jun 2025 10:52:27 +0200 [thread overview]
Message-ID: <87y0tin8l0.wl-tiwai@suse.de> (raw)
In-Reply-To: <3c6c7fb03375bc4532c3a6af65d78226cb5b9281.camel@mailbox.org>
On Mon, 23 Jun 2025 10:02:30 +0200,
Philipp Stanner wrote:
>
> On Sun, 2025-06-22 at 11:28 +0200, Takashi Iwai wrote:
> > On Sat, 21 Jun 2025 20:52:24 +0200,
> > Alok Tiwari wrote:
> > >
> > > code mistakenly used a hardcoded index (codec[1]) instead of
> > > iterating, over the codec array using the loop variable i.
> > > Use codec[i] instead of codec[1] to match the loop iteration.
> > >
> > > Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
> >
> > Applied now. Thanks.
>
> Shouldn't that have been a bug fix with
>
> Fixes:
> and
> Cc: stable
>
> ?
This change likely won't influence on the existing devices, and the
issue has been present from the very beginning of the driver code,
hence no regression.
The stuff in question is about the hardware of over 20 years ago, and
there has been no bug reports about this. After all, all devices were
with at most two codecs, and this patch is for 3rd and 4th codecs.
thanks,
Takashi
prev parent reply other threads:[~2025-06-23 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 18:52 [PATCH] ALSA: intel8x0: Fix incorrect codec index usage in mixer for ICH4 Alok Tiwari
2025-06-22 9:28 ` Takashi Iwai
2025-06-23 8:02 ` Philipp Stanner
2025-06-23 8:52 ` Takashi Iwai [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=87y0tin8l0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alok.a.tiwari@oracle.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=phasta@kernel.org \
--cc=phasta@mailbox.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.