From: Mark Brown <broonie@sirena.org.uk>
To: Steve Sakoman <sakoman@gmail.com>,
linux-omap@vger.kernel.org, alsa-devel@alsa-project.org,
Tony Lindgren <tony@atomide.com>,
David Brownell <david-b@pacbell.net>, Felipe Contreras <f>
Subject: Re: [PATCH] alsa: add beagleboard SoC configuration.
Date: Thu, 30 Oct 2008 11:45:21 +0000 [thread overview]
Message-ID: <20081030114520.GC5747@sirena.org.uk> (raw)
In-Reply-To: <20081022204445.GC7537@sirena.org.uk>
On Wed, Oct 22, 2008 at 09:44:48PM +0100, Mark Brown wrote:
> On Wed, Oct 22, 2008 at 01:30:26PM -0700, Steve Sakoman wrote:
> > I am happy to resubmit the patches, if that is what folks want. I'm
> > copying alsa-devel so they can weigh in on the decision.
> Once mainline is merged up to the ASoC topic branch it should be fine to
> go via ALSA. I've got some other stuff waiting for that to happen
> myself so if you want to send a patch queue I can queue that in there.
> I was going to wait for rc1 before asking Takashi to merge up to the
> ASoC branches.
Ping? I'd like to start pushing more ASoC v2 stuff soon - that means
more API churn so it'd be easier to get as much stuff merged as
possible.
next prev parent reply other threads:[~2008-10-30 11:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 16:28 [PATCH] alsa: add beagleboard SoC configuration Felipe Contreras
2008-10-22 16:53 ` Tony Lindgren
2008-10-22 19:36 ` David Brownell
2008-10-22 20:30 ` Steve Sakoman
2008-10-22 20:44 ` Mark Brown
2008-10-30 11:45 ` Mark Brown [this message]
2008-10-30 13:14 ` Steve Sakoman
2008-10-22 19:09 ` David Brownell
2008-10-24 19:03 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2008-09-16 20:51 [PATCH] alsa: add Beagleboard " Felipe Contreras
2008-09-17 6:19 ` Jarkko Nikula
2008-09-17 12:15 ` Steve Sakoman
2008-10-04 6:34 ` David Brownell
2008-10-06 15:09 ` Paul Walmsley
2008-10-06 18:01 ` David Brownell
2008-10-06 18:32 ` Felipe Balbi
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=20081030114520.GC5747@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.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