From: jeffy <jeffy.chen@rock-chips.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, dianders@chromium.org,
Heiko Stuebner <heiko@sntech.de>,
Liam Girdwood <lgirdwood@gmail.com>,
briannorris@chromium.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, mka@chromium.org,
Takashi Iwai <tiwai@suse.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH v2 3/3] ASoC: rockchip: Init dapm routes dynamically
Date: Tue, 19 Sep 2017 20:44:35 +0800 [thread overview]
Message-ID: <59C11133.5090400@rock-chips.com> (raw)
In-Reply-To: <20170919122803.kybaln43yho3deih@sirena.co.uk>
Hi Mark,
On 09/19/2017 08:28 PM, Mark Brown wrote:
> On Mon, Sep 18, 2017 at 07:18:01PM +0800, Jeffy Chen wrote:
>> Currently we are using a fixed list of dapm routes.
>>
>> Init dapm routes dynamically when parsing dailinks, since we are
>> supporting optional codecs.
>
> This doesn't apply against current code, please check and resend.
>
i rebased these patches to for-next 20170919, but nothing changed...
but i found my other pending patch
(https://patchwork.kernel.org/patch/9958055) might conflict to this,
i'll send a new series to put all my patches together and solve the
conflict...
sorry for the trouble..
WARNING: multiple messages have this Message-ID (diff)
From: jeffy.chen@rock-chips.com (jeffy)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH v2 3/3] ASoC: rockchip: Init dapm routes dynamically
Date: Tue, 19 Sep 2017 20:44:35 +0800 [thread overview]
Message-ID: <59C11133.5090400@rock-chips.com> (raw)
In-Reply-To: <20170919122803.kybaln43yho3deih@sirena.co.uk>
Hi Mark,
On 09/19/2017 08:28 PM, Mark Brown wrote:
> On Mon, Sep 18, 2017 at 07:18:01PM +0800, Jeffy Chen wrote:
>> Currently we are using a fixed list of dapm routes.
>>
>> Init dapm routes dynamically when parsing dailinks, since we are
>> supporting optional codecs.
>
> This doesn't apply against current code, please check and resend.
>
i rebased these patches to for-next 20170919, but nothing changed...
but i found my other pending patch
(https://patchwork.kernel.org/patch/9958055) might conflict to this,
i'll send a new series to put all my patches together and solve the
conflict...
sorry for the trouble..
WARNING: multiple messages have this Message-ID (diff)
From: jeffy <jeffy.chen@rock-chips.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, briannorris@chromium.org,
mka@chromium.org, dianders@chromium.org,
Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH v2 3/3] ASoC: rockchip: Init dapm routes dynamically
Date: Tue, 19 Sep 2017 20:44:35 +0800 [thread overview]
Message-ID: <59C11133.5090400@rock-chips.com> (raw)
In-Reply-To: <20170919122803.kybaln43yho3deih@sirena.co.uk>
Hi Mark,
On 09/19/2017 08:28 PM, Mark Brown wrote:
> On Mon, Sep 18, 2017 at 07:18:01PM +0800, Jeffy Chen wrote:
>> Currently we are using a fixed list of dapm routes.
>>
>> Init dapm routes dynamically when parsing dailinks, since we are
>> supporting optional codecs.
>
> This doesn't apply against current code, please check and resend.
>
i rebased these patches to for-next 20170919, but nothing changed...
but i found my other pending patch
(https://patchwork.kernel.org/patch/9958055) might conflict to this,
i'll send a new series to put all my patches together and solve the
conflict...
sorry for the trouble..
next prev parent reply other threads:[~2017-09-19 12:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 11:17 [RESEND PATCH v2 1/3] ASoC: rockchip: Add dapm route for HDMI Jeffy Chen
2017-09-18 11:17 ` Jeffy Chen
2017-09-18 11:17 ` Jeffy Chen
2017-09-18 11:18 ` [RESEND PATCH v2 2/3] ASoC: rockchip: Add dapm route for DMic Jeffy Chen
2017-09-18 11:18 ` Jeffy Chen
2017-09-18 11:18 ` [RESEND PATCH v2 3/3] ASoC: rockchip: Init dapm routes dynamically Jeffy Chen
2017-09-18 11:18 ` Jeffy Chen
2017-09-19 12:28 ` Mark Brown
2017-09-19 12:28 ` Mark Brown
2017-09-19 12:44 ` jeffy [this message]
2017-09-19 12:44 ` jeffy
2017-09-19 12:44 ` jeffy
2017-09-19 12:19 ` [RESEND PATCH v2 1/3] ASoC: rockchip: Add dapm route for HDMI Mark Brown
2017-09-19 12:19 ` Mark Brown
2017-09-19 12:37 ` jeffy
2017-09-19 12:37 ` jeffy
2017-09-19 12:37 ` jeffy
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=59C11133.5090400@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=alsa-devel@alsa-project.org \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mka@chromium.org \
--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 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.