From: "Agrawal, Akshu" <Akshu.Agrawal@amd.com>
To: Mark Brown <broonie@kernel.org>
Cc: djkurtz@chromium.org, Alexander.Deucher@amd.com,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
"Mukunda, Vijendar" <Vijendar.Mukunda@amd.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Wei Yongjun <weiyongjun1@huawei.com>,
Guenter Roeck <linux@roeck-us.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER
MANAGEM..." <alsa-devel@alsa-project.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [v2, 2/2] ASoC: AMD: Configure channel 1 or channel 0 for capture
Date: Thu, 21 Jun 2018 10:18:04 +0530 [thread overview]
Message-ID: <d3c0ff79-e2ae-a8e9-5e58-8ab003364062@amd.com> (raw)
In-Reply-To: <20180620140257.GG6242@sirena.org.uk>
On 6/20/2018 7:32 PM, Mark Brown wrote:
> On Thu, Jun 07, 2018 at 02:48:44PM +0800, Akshu Agrawal wrote:
>
>> This patch is dependent on ASoC: AMD: Change codec to channel link as per hardware redesign
>> https://patchwork.kernel.org/patch/10388099/
>
> Can you please send a patch series with all the pending changes for this
> driver? It's getting really difficult to track which of the patches
> you've sent fit together and what's currently pending as there's often
> quite a few different AMD patch serieses in flight with interdependencies.
>
Sure, Mark. There are just 2 patches remaining. Will send them as a series.
Thanks,
Akshu
next prev parent reply other threads:[~2018-06-21 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 6:48 [PATCH 1/2] ASoC: AMD: Add NULL pointer check Akshu Agrawal
2018-06-07 6:48 ` [v2, 2/2] ASoC: AMD: Configure channel 1 or channel 0 for capture Akshu Agrawal
2018-06-20 14:02 ` Mark Brown
2018-06-21 4:48 ` Agrawal, Akshu [this message]
2018-06-22 14:50 ` Applied "ASoC: AMD: Configure channel 1 or channel 0 for capture" to the asoc tree Mark Brown
2018-06-18 12:00 ` Applied "ASoC: AMD: Add NULL pointer check" " Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2018-06-21 4:58 [PATCH 1/2] ASoC: AMD: Change codec to channel link as per hardware redesign Akshu Agrawal
2018-06-21 4:58 ` [v2, 2/2] ASoC: AMD: Configure channel 1 or channel 0 for capture Akshu Agrawal
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=d3c0ff79-e2ae-a8e9-5e58-8ab003364062@amd.com \
--to=akshu.agrawal@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=djkurtz@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=weiyongjun1@huawei.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