From: Tony Lindgren <tony@atomide.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: Jorge Eduardo Candelaria <jorge.candelaria@ti.com>,
linux-omap@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
Jarkko Nikula <jhnikula@gmail.com>,
alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v3 0/2] McBSP changes for OMAP4 platform
Date: Thu, 13 May 2010 17:14:57 -0700 [thread overview]
Message-ID: <20100514001456.GR3428@atomide.com> (raw)
In-Reply-To: <1273742970.3316.14.camel@odin>
* Liam Girdwood <lrg@slimlogic.co.uk> [100513 02:24]:
> On Thu, 2010-05-13 at 09:19 +0100, Mark Brown wrote:
> > On Wed, May 12, 2010 at 12:18:38PM -0500, Jorge Eduardo Candelaria wrote:
> > > The following patches enable McBSP driver to be used along with the
> > > audio driver in SDP4430 and other OMAP4 based boards.
> >
> > Both
> >
> > Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>
> Tony, do we have you ack/sob to upstream via ASoC ?
No problem with me, both of them:
Acked-by: Tony Lindgren <tony@atomide.com>
> We do have a lot pending with mcbsp dependencies for ASoC atm and this
> would simplify upstreaming.
Sure, I agree. It's best to keep the patchsets toghether.
One request I have for the long run is to set some features
flag during init and only use the cpu_is_omapxxxx tests once
during init. That way the driver is more future proof and
should not require adding cpu_is_omapxxxx all over the place.
Regards,
Tony
prev parent reply other threads:[~2010-05-14 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1273684720-16619-1-git-send-email-jorge.candelaria@ti.com>
[not found] ` <20100513081947.GB19774@opensource.wolfsonmicro.com>
2010-05-13 9:29 ` [PATCH v3 0/2] McBSP changes for OMAP4 platform Liam Girdwood
2010-05-14 0:14 ` Tony Lindgren [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=20100514001456.GR3428@atomide.com \
--to=tony@atomide.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jhnikula@gmail.com \
--cc=jorge.candelaria@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.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 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).