From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>
Cc: perex@perex.cz, tiwai@suse.com, phasta@kernel.org,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] ALSA: intel8x: Why incorrect codec index used setting ICH_DI2L SDIN
Date: Thu, 19 Jun 2025 18:38:57 +0300 [thread overview]
Message-ID: <aFQvEYdQfiJn-29o@smile.fi.intel.com> (raw)
In-Reply-To: <20250618191929.2382821-1-alok.a.tiwari@oracle.com>
On Wed, Jun 18, 2025 at 12:19:21PM -0700, Alok Tiwari wrote:
> Correct the index to use codec[i] to match the loop iteration, not codec[1].
>
> Is this a mistake or intentional?
You marked it as a BUG in the Subject, can you elaborate more, please?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-06-19 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 19:19 [BUG] ALSA: intel8x: Why incorrect codec index used setting ICH_DI2L SDIN Alok Tiwari
2025-06-19 15:38 ` Andy Shevchenko [this message]
2025-06-19 19:26 ` [External] : " ALOK TIWARI
2025-06-20 8:11 ` Takashi Iwai
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=aFQvEYdQfiJn-29o@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alok.a.tiwari@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=phasta@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox