From: David Brownell <david-b@pacbell.net>
To: Mark Brown <broonie@sirena.org.uk>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Steve Sakoman <steve@sakoman.com>
Subject: Re: [alsa-devel] [patch] bugfix: SOUND: SOC: OMAP: Add support for Gumstix Overo
Date: Fri, 3 Oct 2008 08:37:14 -0700 [thread overview]
Message-ID: <200810030837.15131.david-b@pacbell.net> (raw)
In-Reply-To: <20081003151846.GA9127@sirena.org.uk>
On Friday 03 October 2008, Mark Brown wrote:
> > ---
> > I'm not sure where the four patches for Overo support are
> > in the ALSA queue (that's how they'll merge, yes?) but I'll
> > suggest this one merge into the initial "overo.c" submit...
>
> They're not queued in ALSA since they depend on the PMIC codec driver
> which in turn depends on the PMIC core driver being merged.
I'm working on getting the twl4030 core merged ... expecting
it to be there for 2.6.28-early. Since this codec driver
doesn't need interrupts, it's particularly undemanding. :)
So if the only place these are queued is the OMAP tree, and
there is no particular objection to the patch, then there'd
seem be no issue merging it to the OMAP tree and having it
be part of the initial merge-to-mainline...
- Dave
next prev parent reply other threads:[~2008-10-03 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 15:11 [patch] bugfix: SOUND: SOC: OMAP: Add support for Gumstix Overo David Brownell
2008-10-03 15:18 ` [alsa-devel] " Mark Brown
2008-10-03 15:37 ` David Brownell [this message]
2008-10-03 17:49 ` Mark Brown
2008-10-04 7:10 ` Tony Lindgren
2008-10-06 6:48 ` Tony Lindgren
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=200810030837.15131.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=steve@sakoman.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.