From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Ben Dooks <ben@trinity.fluff.org>
Cc: "Graeme.Gregory" <Graeme.Gregory@wolfsonmicro.com>,
alsa-devel@lists.sourceforge.net
Subject: Re: ASoC merge plans
Date: Mon, 29 Jan 2007 14:02:19 +0000 [thread overview]
Message-ID: <1170079339.31420.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20070129125837.GE12669@trinity.fluff.org>
Hi Ben,
On Mon, 2007-01-29 at 12:58 +0000, Ben Dooks wrote:
> What is the current merge plans for getting ASoC
> into the kernel? is there any specific timeline?
>
Were working hard atm trying to get 0.13 released and ready for the next
merge kernel window (0.12 is already in alsa-kernel). This will include
AT91xx and pxa2xx platform support and corgi, tosa, borzoi, poodle, HTC
magician and eti_b1 machine support.
> I am specifically interested in the S3C24xx series
> as this is what most of my current work is with.
S3C24xx platform support is pretty much working well now (probably could
do with a little more testing). Your patches made this quite easy :) I
think we should probably proceed and try for S3C24xx support 2.6.21.
Takashi, when do you and Jaroslav intend to push alsa-kernel in this
merge window. Do you have a date in mind that I can target for the next
release ?
Cheers
Liam
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-01-29 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 12:58 ASoC merge plans Ben Dooks
2007-01-29 13:41 ` Takashi Iwai
2007-01-29 14:02 ` Liam Girdwood [this message]
2007-01-29 14:10 ` Takashi Iwai
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=1170079339.31420.30.camel@localhost.localdomain \
--to=lg@opensource.wolfsonmicro.com \
--cc=Graeme.Gregory@wolfsonmicro.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ben@trinity.fluff.org \
/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.