From: "christian pellegrin" <chripell@gmail.com>
To: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Cc: zdevai@gmail.com, alsa-devel@alsa-project.org,
Mark Brown <broonie@sirena.org.uk>,
Ben Dooks <ben-linux@fluff.org>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] ALSA SOC driver for s3c24xx with uda1341
Date: Wed, 12 Nov 2008 07:31:46 +0100 [thread overview]
Message-ID: <cabda6420811112231q4c6e4ec1vec7626f11f59fe62@mail.gmail.com> (raw)
In-Reply-To: <20081111215317.091d870d.kristoffer.ericson@gmail.com>
On Tue, Nov 11, 2008 at 9:53 PM, Kristoffer Ericson
<kristoffer.ericson@gmail.com> wrote:
> On Tue, 11 Nov 2008 15:15:11 +0100
>
> Oh, just wanted to ask, is the L3 code platform specific
> or universally crunchable?
>
In the patch that is coming it will be more reusable.
--
Christian Pellegrin, see http://www.evolware.org/chri/
"Real Programmers don't play tennis, or any other sport which requires
you to change clothes. Mountain climbing is OK, and Real Programmers
wear their climbing boots to work in case a mountain should suddenly
spring up in the middle of the computer room."
next prev parent reply other threads:[~2008-11-12 6:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 7:43 [PATCH] ALSA SOC driver for s3c24xx with uda1341 Christian Pellegrin
2008-11-10 13:34 ` Mark Brown
2008-11-10 17:58 ` Kristoffer Ericson
2008-11-10 19:08 ` chri
2008-11-10 20:22 ` Kristoffer Ericson
2008-11-10 22:10 ` [alsa-devel] " Ben Dooks
2008-11-11 14:15 ` chri
2008-11-11 18:55 ` Kristoffer Ericson
2008-11-11 20:53 ` Kristoffer Ericson
2008-11-12 6:31 ` christian pellegrin [this message]
2008-11-10 19:04 ` chri
2008-11-11 10:39 ` Mark Brown
2008-11-11 14:16 ` chri
2008-11-10 19:22 ` [alsa-devel] " Russell King - ARM Linux
2008-11-11 14:00 ` chri
2008-11-10 22:09 ` Ben Dooks
2008-11-11 14:14 ` chri
2008-11-11 15:52 ` Mark Brown
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=cabda6420811112231q4c6e4ec1vec7626f11f59fe62@mail.gmail.com \
--to=chripell@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@sirena.org.uk \
--cc=kristoffer.ericson@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=zdevai@gmail.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.