From: Mengdong Lin <mengdong.lin@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, vinod.koul@intel.com,
mengdong.lin@intel.com, liam.r.girdwood@linux.intel.com,
jeeja.kp@intel.com, subhransu.s.prusty@intel.com
Subject: Re: [PATCH v2 0/2] ASoC: Change the PCM runtime array to a list
Date: Thu, 19 Nov 2015 04:30:56 -0500 [thread overview]
Message-ID: <564D96D0.3030305@linux.intel.com> (raw)
In-Reply-To: <20151118183021.GK31303@sirena.org.uk>
On 11/18/2015 01:30 PM, Mark Brown wrote:
> On Wed, Nov 18, 2015 at 02:31:26AM -0500, mengdong.lin@linux.intel.com wrote:
>> From: Mengdong Lin <mengdong.lin@linux.intel.com>
>>
>> The 2 patches are a preparation to allow the topology core to create
>> PCM devices dynamically. Probing a component may load its topology and
>> come up with new DAI links and thus new runtimes. So implementing the
>> PCM runtimes in a list makes it easier to add new runtimes.
>
> I've got two apparently identical copies of this series that have
> threaded together into one thread. I'm going to look at what looks like
> the newer copy but I might get it wrong, please check.
>
Hi Mark,
Thanks for your review!
These two series are exactly same. Since the 1st one has no feedback for
~2 weeks, I thought it may be buried by the mail flood and so sent again
yesterday.
I'll send the following patches.
Regards
Mengdong
prev parent reply other threads:[~2015-11-19 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 3:30 [PATCH v2 0/2] ASoC: Change the PCM runtime array to a list mengdong.lin
2015-11-05 3:31 ` [PATCH v2 1/2] ASoC: Vendor drivers get a link's runtime by snd_soc_get_pcm_runtime() mengdong.lin
2015-11-05 3:31 ` [PATCH v2 2/2] ASoC: Change the PCM runtime array to a list mengdong.lin
2015-11-18 18:32 ` Applied "ASoC: Change the PCM runtime array to a list" to the asoc tree Mark Brown
2015-11-18 18:30 ` [PATCH v2 0/2] ASoC: Change the PCM runtime array to a list Mark Brown
2015-11-19 9:30 ` Mengdong Lin [this message]
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=564D96D0.3030305@linux.intel.com \
--to=mengdong.lin@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jeeja.kp@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mengdong.lin@intel.com \
--cc=subhransu.s.prusty@intel.com \
--cc=vinod.koul@intel.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.