From: Mark Brown <broonie@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Jaroslav Kysela <jkysela@redhat.com>,
Mukunda Vijendar <Vijendar.Mukunda@amd.com>,
Saba Kareem Syed <Syed.SabaKareem@amd.com>,
linux-kernel@vger.kernel.org,
Pananchikkal Renjith <Renjith.Pananchikkal@amd.com>,
Mark Pearson <mpearson@lenovo.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v3 1/6] ASoC: amd: yc: Adjust the gain for PDM DMIC
Date: Thu, 2 Feb 2023 13:42:28 +0000 [thread overview]
Message-ID: <Y9u9xCNDd8R0Zi08@sirena.org.uk> (raw)
In-Reply-To: <270a6bf0-8774-2f0d-9b0e-4f1eb9a986e6@amd.com>
[-- Attachment #1: Type: text/plain, Size: 126 bytes --]
On Thu, Feb 02, 2023 at 07:38:55AM -0600, Mario Limonciello wrote:
> Would you like me to resend the series?
No, it's fine.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-02 13:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 18:46 [PATCH v3 0/6] Fix default DMIC gain on AMD PDM drivers Mario Limonciello
2023-01-31 18:46 ` [PATCH v3 1/6] ASoC: amd: yc: Adjust the gain for PDM DMIC Mario Limonciello
2023-02-02 11:42 ` Mark Brown
2023-02-02 13:38 ` Mario Limonciello
2023-02-02 13:42 ` Mark Brown [this message]
2023-01-31 18:46 ` [PATCH v3 2/6] ASoC: amd: yc: Add a module parameter to influence pdm_gain Mario Limonciello
2023-01-31 18:46 ` [PATCH v3 3/6] ASoC: amd: renoir: Adjust the gain for PDM DMIC Mario Limonciello
2023-01-31 18:46 ` [PATCH v3 4/6] ASoC: amd: renoir: Add a module parameter to influence pdm_gain Mario Limonciello
2023-01-31 18:46 ` [PATCH v3 5/6] ASoC: amd: ps: Adjust the gain for PDM DMIC Mario Limonciello
2023-01-31 18:46 ` [PATCH v3 6/6] ASoC: amd: ps: Add a module parameter to influence pdm_gain Mario Limonciello
2023-01-31 18:51 ` [PATCH v3 0/6] Fix default DMIC gain on AMD PDM drivers Jaroslav Kysela
2023-02-02 15:37 ` 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=Y9u9xCNDd8R0Zi08@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Renjith.Pananchikkal@amd.com \
--cc=Syed.SabaKareem@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=jkysela@redhat.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mpearson@lenovo.com \
--cc=perex@perex.cz \
--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
all inboxes | Powered by JetHome®