From: Jarkko Nikula <jhnikula@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>,
Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
Liam Girdwood <lrg@slimlogic.co.uk>,
alsa-devel@alsa-project.org,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
e3-hacking@earth.li
Subject: Re: [PATCH 2.6.37-rc1] ASoC: OMAP: fix OMAP1 compilation problem
Date: Thu, 25 Nov 2010 09:02:01 +0200 [thread overview]
Message-ID: <20101125090201.256972a4.jhnikula@gmail.com> (raw)
In-Reply-To: <20101124235342.GC31536@atomide.com>
On Wed, 24 Nov 2010 15:53:42 -0800
Tony Lindgren <tony@atomide.com> wrote:
> * Tony Lindgren <tony@atomide.com> [101124 15:25]:
> >
> > Anyways, Paul's patch should be merged during the -rc cycle
> > because it is currently blocking Amstrad delta being built:
> >
> > http://armlinux.simtec.co.uk/kautobuild/
>
> Turns out I'm several hours behind.. The build is
> working with Janusz commit 233538501f707b0176f09af7039fec1e3fcac6e7
> now in mainline.
>
> I guess no need to merge Paul's fix then?
>
Not necessary I think if compilers are happy with Janusz's fix. If not,
then very strong reasong to start looking for platform data solution
as soon as possible :-)
--
Jarkko
next prev parent reply other threads:[~2010-11-25 7:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 14:50 [PATCH 2.6.37-rc1] ASoC: OMAP: fix OMAP1 compilation problem Janusz Krzysztofik
2010-11-02 14:56 ` Mark Brown
2010-11-02 16:58 ` Paul Walmsley
2010-11-03 8:20 ` Jarkko Nikula
2010-11-03 14:16 ` [alsa-devel] " Liam Girdwood
2010-11-23 0:48 ` Paul Walmsley
2010-11-23 7:26 ` Jarkko Nikula
2010-11-23 10:32 ` [alsa-devel] " Liam Girdwood
2010-11-24 23:35 ` Tony Lindgren
2010-11-24 23:53 ` Tony Lindgren
2010-11-25 7:02 ` Jarkko Nikula [this message]
2010-11-25 12:47 ` Janusz Krzysztofik
2010-11-25 17:45 ` Paul Walmsley
2010-11-23 0:50 ` Paul Walmsley
[not found] ` <alpine.DEB.2.00.1011221748410.20215@utopia.booyaka.com>
2010-11-23 7:38 ` Jarkko Nikula
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=20101125090201.256972a4.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=e3-hacking@earth.li \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=paul@pwsan.com \
--cc=peter.ujfalusi@nokia.com \
--cc=tony@atomide.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).