From: Timur Tabi <timur@freescale.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: MPC8610HPCD sound as module
Date: Thu, 11 Dec 2008 13:17:57 -0600 [thread overview]
Message-ID: <49416765.5090101@freescale.com> (raw)
In-Reply-To: <20081211185255.GA16784@sirena.org.uk>
Mark Brown wrote:
> Well, from that point of view now would be a good time for you to start
> backporting your newer code. The concept of having the core wait for
> subdevices to probe is now there which was the major win from the point
> of view of integration with the device tree. What's there now also has
> the changes you wanted without the use of templates in the ASoC core so
> you can do a single memory allocation for devices rather than having to
> fill out templates and have the core do allocations for you.
Okee dokee. I'll start working on it next month.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2008-12-11 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 13:18 MPC8610HPCD sound as module Peter Czanik
2008-12-11 15:12 ` Timur Tabi
2008-12-11 15:31 ` Mark Brown
2008-12-11 15:40 ` Timur Tabi
2008-12-11 15:44 ` Mark Brown
2008-12-11 15:45 ` Timur Tabi
2008-12-11 18:52 ` Mark Brown
2008-12-11 19:17 ` Timur Tabi [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=49416765.5090101@freescale.com \
--to=timur@freescale.com \
--cc=broonie@sirena.org.uk \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).