From: Jarkko Nikula <jhnikula@gmail.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Peter Ujfalusi <peter.ujfalusi@nokia.com>,
Mark Brown <broonie@opensource.wolfsonmicro.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, tony@atomide.com,
Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Subject: Re: [PATCH 2.6.37-rc1] ASoC: OMAP: fix OMAP1 compilation problem
Date: Tue, 23 Nov 2010 09:38:43 +0200 [thread overview]
Message-ID: <20101123093843.23e4d579.jhnikula@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1011221748410.20215@utopia.booyaka.com>
On Mon, 22 Nov 2010 17:50:54 -0700 (MST)
Paul Walmsley <paul@pwsan.com> wrote:
>
> By the way, ASoC and OMAP audio-hackers, I deeply regret how much trouble
> that SCM cleanup series has caused. It does not meet my personal
> standards for a patch-series...
>
Hey, small compile breaks happens to everyone and word trouble doesn't
come to my mind when speaking about your set.
Your set actually did one major step forward with ASoC OMAP drivers -
now it's possible to have modular build with them so your work has lot
of benefits to developers and distro builders.
--
Jarkko
prev parent reply other threads:[~2010-11-23 7:38 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
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 [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=20101123093843.23e4d579.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).