From: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Vijendar.Mukunda@amd.com,
Basavaraj.Hiregoudar@amd.com, Sunil-kumar.Dommati@amd.com,
Alexander.Deucher@amd.com, Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/8] ASoC: amd: Add common framework to support I2S on ACP SOC
Date: Tue, 19 Oct 2021 12:58:36 +0530 [thread overview]
Message-ID: <02868f8d-fee4-bfe3-04c4-5d0517bd6c74@amd.com> (raw)
In-Reply-To: <YW3VUMT9Rjs2+A1G@sirena.org.uk>
I've rebased on top of current code and submitted new patch chain after
resolving conflicts. Please try applying now
https://patchwork.kernel.org/project/alsa-devel/list/?series=566025.
Thanks & Regards
Ajit
On 10/19/2021 1:43 AM, Mark Brown wrote:
> [CAUTION: External Email]
>
next prev parent reply other threads:[~2021-10-19 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211012071939.97002-1-AjitKumar.Pandey@amd.com>
2021-10-12 7:19 ` Ajit Kumar Pandey
2021-10-18 20:13 ` Mark Brown
2021-10-19 7:28 ` Ajit Kumar Pandey [this message]
2021-10-12 7:19 ` [PATCH v3 2/8] ASoC: amd: acp: Add I2S support on Renoir platform Ajit Kumar Pandey
2021-10-12 7:19 ` [PATCH v3 3/8] ASoC: amd: acp: Add callback for machine driver on ACP Ajit Kumar Pandey
2021-10-12 7:19 ` [PATCH v3 4/8] ASoC: amd: acp: Add generic machine driver support for ACP cards Ajit Kumar Pandey
2021-10-12 7:19 ` [PATCH v3 5/8] ASoC: amd: acp: Add legacy sound card support for Chrome audio Ajit Kumar Pandey
2021-10-12 7:19 ` [PATCH v3 6/8] ASoC: amd: acp: Add SOF audio support on Chrome board Ajit Kumar Pandey
2021-10-12 7:19 ` [PATCH v3 7/8] ASoC: amd: acp: Add support for Maxim amplifier codec Ajit Kumar Pandey
2021-10-12 7:19 ` [PATCH v3 8/8] ASoC: amd: acp: Add support for RT5682-VS codec Ajit Kumar Pandey
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=02868f8d-fee4-bfe3-04c4-5d0517bd6c74@amd.com \
--to=ajitkumar.pandey@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--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®