public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
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..

  reply	other threads:[~2017-09-19 12:44 UTC|newest]

Thread overview: 7+ 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:18 ` [RESEND PATCH v2 2/3] ASoC: rockchip: Add dapm route for DMic Jeffy Chen
2017-09-18 11:18 ` [RESEND PATCH v2 3/3] ASoC: rockchip: Init dapm routes dynamically Jeffy Chen
2017-09-19 12:28   ` Mark Brown
2017-09-19 12:44     ` jeffy [this message]
2017-09-19 12:19 ` [RESEND PATCH v2 1/3] ASoC: rockchip: Add dapm route for HDMI Mark Brown
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$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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