From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jarkko.nikula@nokia.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ASoC for TI OMAP - alsa-devel submission?
Date: Wed, 2 Apr 2008 12:00:54 +0100 [thread overview]
Message-ID: <20080402110054.GA7977@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20080402134530.3460b0bf.jarkko.nikula@nokia.com>
On Wed, Apr 02, 2008 at 01:45:30PM +0300, Jarkko Nikula wrote:
> So what I mean that should I post the patch like as it now, rebased to
> dev branch of linux-2.6-asoc tree and with some minor changes, or wait a
> bit when all linux-omap and ASoC v2 evolve? What you think?
Whatever is most convenient for you. From the point of view of getting
stuff in immediately it's best to base things on ASoC v1 though from an
ongoing development point of view ASoC v2 is a better target if you can
cope with any churn and hopefully we should be starting to push it into
the kernel within the next couple of release cycles so if it's going to
take a while to get the required BSP changes in...
next prev parent reply other threads:[~2008-04-02 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 10:45 ASoC for TI OMAP - alsa-devel submission? Jarkko Nikula
2008-04-02 11:00 ` Mark Brown [this message]
2008-04-03 5:56 ` 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=20080402110054.GA7977@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@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