From: qby140326 <qby140326@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>, vijendar.mukunda@amd.com
Cc: broonie@kernel.org, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.com, venkataprasad.potturu@amd.com,
Sunil-kumar.Dommati@amd.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: amd: add DMIC support for RPL platform
Date: Thu, 12 Feb 2026 09:42:52 +0800 [thread overview]
Message-ID: <a68b5c3f-3938-4402-80fa-08da74b87405@gmail.com> (raw)
In-Reply-To: <a33d3400-81e0-4090-873b-7687acab4893@amd.com>
On 2/11/26 23:21, Mario Limonciello wrote:
> Your diff should be relative to sound.git, not relative to your last
> patch.
>
> That means you shouldn't be "deleting the rpl directory" because it
> isn't there in upstream.
>
> On your local tree you can probably just rebase to drop it or revert it.
Hi Mario,
Regarding the sound/soc/amd/rpl directory, I believe it actually exists
in the current upstream sound.git (and mainline). You can find it here:
sound/soc/amd/rpl/
The goal of this patch is to follow the suggestion from Vijendar Mukunda
to consolidate the RPL support into the yc driver, as they share very
similar logic. By doing this, we can completely remove the redundant rpl
folder to simplify the codebase.
PS: I noticed the Makefile and Kconfig problem, I'll create the v3 patch
shortly to ensure everything builds correctly.
next prev parent reply other threads:[~2026-02-12 1:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 2:07 [PATCH] " Mingyou Chen
2026-02-06 17:51 ` Mark Brown
2026-02-07 1:44 ` qby140326
2026-02-07 5:50 ` Mukunda,Vijendar
2026-02-07 12:45 ` Mark Brown
2026-02-11 9:22 ` Mukunda,Vijendar
2026-02-11 10:46 ` qby140326
2026-02-11 11:16 ` qby140326
2026-02-11 11:19 ` Mukunda,Vijendar
2026-02-11 11:50 ` [PATCH v2] " Mingyou Chen
2026-02-11 15:21 ` Mario Limonciello
2026-02-12 1:42 ` qby140326 [this message]
2026-02-12 1:46 ` [PATCH v3] " Mingyou Chen
2026-02-12 5:13 ` Mukunda,Vijendar
2026-02-12 11:15 ` [PATCH v4] " Mingyou Chen
2026-02-12 13:26 ` Mark Brown
2026-02-12 13:45 ` Mario Limonciello
2026-02-11 17:13 ` [PATCH v2] " kernel test robot
2026-02-11 22:35 ` kernel test robot
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=a68b5c3f-3938-4402-80fa-08da74b87405@gmail.com \
--to=qby140326@gmail.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@amd.com \
--cc=vijendar.mukunda@amd.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
all inboxes | Powered by JetHome®