From: Mark Brown <broonie@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: tiwai@suse.de, linux-sound@vger.kernel.org, bard.liao@intel.com,
shumingf@realtek.com
Subject: Re: [PATCH] ASoC: sdw_utils: add name_prefix for rt1321 part id
Date: Wed, 22 Oct 2025 13:04:34 +0100 [thread overview]
Message-ID: <d7f93bbd-29cc-4c81-8e76-7b47f59b4e2d@sirena.org.uk> (raw)
In-Reply-To: <20251022073952.327451-1-yung-chuan.liao@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
On Wed, Oct 22, 2025 at 03:39:52PM +0800, Bard Liao wrote:
> From: Shuming Fan <shumingf@realtek.com>
>
> This patch adds name_prefix for rt1321 part id in the codec_info_list.
It's OK this time but this changelog just says what the patch does, it
doesn't explain why the change is being made.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-10-22 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 7:39 [PATCH] ASoC: sdw_utils: add name_prefix for rt1321 part id Bard Liao
2025-10-22 12:04 ` Mark Brown [this message]
2025-10-22 22:42 ` Mark Brown
2025-10-24 10:23 ` Mark Brown
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=d7f93bbd-29cc-4c81-8e76-7b47f59b4e2d@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bard.liao@intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=shumingf@realtek.com \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@linux.intel.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