From: Hasun Park <hasunpark@gmail.com>
To: broonie@kernel.org
Cc: Vijendar.Mukunda@amd.com, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
perex@perex.cz, tiwai@suse.com, venkataprasad.potturu@amd.com,
Hasun Park <hasunpark@gmail.com>
Subject: Re: (subset) [PATCH 0/3] ASoC: amd: acp: PX13 ACP70 config and machine quirks
Date: Tue, 17 Mar 2026 01:47:31 +0900 [thread overview]
Message-ID: <20260316164731.18720-1-hasunpark@gmail.com> (raw)
In-Reply-To: <177362009337.162791.6622780298534018366.b4-ty@kernel.org>
>On Mon, 09 Mar 2026 00:16:51 +0900, hasunpark@gmail.com wrote:
>> ASoC: amd: acp: PX13 ACP70 config and machine quirks
>>
>> From: Hasun Park <hasunpark@gmail.com>
>>
>> Hi,
>>
>> This series adds ACP70 platform quirks for ASUS ProArt PX13
>> (HN7306EA/HN7306EAC).
>>
>> [...]
>
>Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.0
>
>Thanks!
Hi Mark. I've done some clean up since that system does not require rt721 for dmic.
After preparing V2 patch series i realized some are already merged on for-next branch.
I'm not sure what should i prefer, send this v2 patch or
since this change is just for cleaning up and doesn't cause problem at function
so submit another patch for cleaning up.
I need your advice. Thanks
next prev parent reply other threads:[~2026-03-16 16:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 15:16 [PATCH 0/3] ASoC: amd: acp: PX13 ACP70 config and machine quirks hasunpark
2026-03-08 15:16 ` [PATCH 1/3] ASoC: amd: acp: add DMI override for ACP70 flag hasunpark
2026-03-09 5:33 ` Mukunda,Vijendar
2026-03-09 11:34 ` Mark Brown
2026-03-09 15:31 ` Mario Limonciello
2026-03-09 15:48 ` Mark Brown
2026-03-08 15:16 ` [PATCH 2/3] ASoC: amd: acp: add PX13 SoundWire machine link for rt721+tas2783x2 hasunpark
2026-03-08 15:16 ` [PATCH 3/3] ASoC: amd: acp: add ASUS HN7306EA quirk for legacy SDW machine hasunpark
2026-03-09 5:37 ` Mukunda,Vijendar
2026-03-11 17:21 ` Mark Brown
2026-03-11 17:32 ` Mukunda,Vijendar
2026-03-12 6:49 ` Mukunda,Vijendar
2026-03-12 13:06 ` Mark Brown
2026-03-15 20:20 ` Eric Naim
2026-03-15 23:53 ` Mark Brown
2026-03-16 2:30 ` Mario Limonciello
2026-03-16 3:50 ` Eric Naim
2026-03-16 15:46 ` Hasun Park
2026-03-17 4:00 ` Mukunda,Vijendar
2026-03-17 17:04 ` Mukunda,Vijendar
2026-03-17 17:22 ` Hasun Park
2026-03-19 16:33 ` [PATCH v2] " Hasun Park
2026-03-19 16:35 ` Mark Brown
2026-03-20 12:53 ` Mark Brown
2026-03-16 0:14 ` (subset) [PATCH 0/3] ASoC: amd: acp: PX13 ACP70 config and machine quirks Mark Brown
2026-03-16 16:47 ` Hasun Park [this message]
2026-03-16 17:45 ` Mark Brown
2026-03-16 17:52 ` 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=20260316164731.18720-1-hasunpark@gmail.com \
--to=hasunpark@gmail.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@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