From: Mark Brown <broonie@kernel.org>
To: qby140326 <qby140326@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Venkata Prasad Potturu <venkataprasad.potturu@amd.com>
Subject: Re: [PATCH] ASoC: amd: add DMIC support for RPL platform
Date: Sat, 7 Feb 2026 12:45:26 +0000 [thread overview]
Message-ID: <aYcz5vlgbtpnMooB@sirena.co.uk> (raw)
In-Reply-To: <6967305c-baed-4f0c-8201-b1610bdefd4e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
On Sat, Feb 07, 2026 at 09:44:28AM +0800, qby140326 wrote:
> Since I don't work for AMD, I'm not in a position to decide who should be
> officially responsible for this.
That comment was addressed at the AMD people I was copying in more than
you.
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-02-07 12:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 2:07 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 [this message]
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
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=aYcz5vlgbtpnMooB@sirena.co.uk \
--to=broonie@kernel.org \
--cc=Vijendar.Mukunda@amd.com \
--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=qby140326@gmail.com \
--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
all inboxes | Powered by JetHome®