From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: Paul Walmsley <paul@pwsan.com>,
alsa-devel@alsa-project.org,
Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
e3-hacking@earth.li,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [alsa-devel] [PATCH 2.6.37-rc1] ASoC: OMAP: fix OMAP1 compilation problem
Date: Wed, 03 Nov 2010 14:16:32 +0000 [thread overview]
Message-ID: <1288793792.3277.51.camel@odin> (raw)
In-Reply-To: <20101103102028.8ff19cac.jhnikula@gmail.com>
On Wed, 2010-11-03 at 10:20 +0200, Jarkko Nikula wrote:
> On Tue, 2 Nov 2010 10:58:59 -0600 (MDT)
> Paul Walmsley <paul@pwsan.com> wrote:
>
> > On Tue, 2 Nov 2010, Janusz Krzysztofik wrote:
> >
> > > In the new code introduced with commit cf4c87abe238ec17cd0255b4e21abd949d7f811e,
> > > "OMAP: McBSP: implement McBSP CLKR and FSR signal muxing via mach-omap2/mcbsp.c",
> > > the way omap1 build is supposed to bypass omap2 specific functionality doesn't
> > > optimize out all omap2 specific stuff. This breaks linking phase for omap1
> > > machines, giving "undefined reference to `omap2_mcbsp1_mux_clkr_src'"
> > > and "undefined reference to `omap2_mcbsp1_mux_fsr_src'" errors. Fix it.
> > >
> > > Created and tested against linux-2.6.37-rc1.
> > >
> > > Signed-off-by: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
> >
> > Acked-by: Paul Walmsley <paul@pwsan.com>
> >
> > Thanks Janusz.
> >
> Yep, this must go to 2.6.37.
>
> Acked-by: Jarkko Nikula <jhnikula@gmail.com>
Applied.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-11-03 14:16 UTC|newest]
Thread overview: 16+ 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 ` Liam Girdwood [this message]
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
2010-11-25 12:47 ` Janusz Krzysztofik
2010-11-25 17:45 ` Paul Walmsley
2010-11-23 0:50 ` Paul Walmsley
2010-11-23 0:50 ` Paul Walmsley
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=1288793792.3277.51.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=e3-hacking@earth.li \
--cc=jhnikula@gmail.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--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 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.