From: Mark Brown <broonie@kernel.org>
To: Akshu Agrawal <akshu.agrawal@amd.com>
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: Wed, 20 Jun 2018 15:02:57 +0100 [thread overview]
Message-ID: <20180620140257.GG6242@sirena.org.uk> (raw)
In-Reply-To: <1528354129-5023-2-git-send-email-akshu.agrawal@amd.com>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Akshu Agrawal <akshu.agrawal@amd.com>
Cc: "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER
MANAGEM..." <alsa-devel@alsa-project.org>,
open list <linux-kernel@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Takashi Iwai <tiwai@suse.com>,
djkurtz@chromium.org, Liam Girdwood <lgirdwood@gmail.com>,
Wei Yongjun <weiyongjun1@huawei.com>,
"Mukunda, Vijendar" <Vijendar.Mukunda@amd.com>,
Alexander.Deucher@amd.com, Guenter Roeck <linux@roeck-us.net>
Subject: Re: [v2, 2/2] ASoC: AMD: Configure channel 1 or channel 0 for capture
Date: Wed, 20 Jun 2018 15:02:57 +0100 [thread overview]
Message-ID: <20180620140257.GG6242@sirena.org.uk> (raw)
In-Reply-To: <1528354129-5023-2-git-send-email-akshu.agrawal@amd.com>
[-- Attachment #1.1: Type: text/plain, Size: 494 bytes --]
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.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-06-20 14:04 UTC|newest]
Thread overview: 14+ 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 ` Akshu Agrawal
2018-06-07 6:48 ` [v2, 2/2] ASoC: AMD: Configure channel 1 or channel 0 for capture Akshu Agrawal
2018-06-07 6:48 ` Akshu Agrawal
2018-06-20 14:02 ` Mark Brown [this message]
2018-06-20 14:02 ` Mark Brown
2018-06-21 4:48 ` Agrawal, Akshu
2018-06-21 4:48 ` Agrawal, Akshu
2018-06-22 14:50 ` Applied "ASoC: AMD: Configure channel 1 or channel 0 for capture" to the asoc tree Mark Brown
2018-06-22 14:50 ` Mark Brown
2018-06-18 12:00 ` Applied "ASoC: AMD: Add NULL pointer check" " Mark Brown
2018-06-18 12:00 ` Mark Brown
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
2018-06-21 4:58 ` 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=20180620140257.GG6242@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Alexander.Deucher@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=akshu.agrawal@amd.com \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.