From: David Brownell <david-b@pacbell.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: broonie@opensource.wolfsonmicro.com, lrg@slimlogic.co.uk,
lkml <linux-kernel@vger.kernel.org>,
DaVinci <davinci-linux-open-source@linux.davincidsp.com>
Subject: Re: [patch 0/3] DaVinci ASoC updates
Date: Fri, 15 May 2009 01:21:16 -0700 [thread overview]
Message-ID: <200905150121.16736.david-b@pacbell.net> (raw)
In-Reply-To: <s5hy6sy23ba.wl%tiwai@suse.de>
On Friday 15 May 2009, Takashi Iwai wrote:
> At Thu, 14 May 2009 12:35:35 -0700,
> David Brownell wrote:
> >
> > The 2.6.30-rc5 merges included a bunch of DaVinci platform
> > updates, including EDMA support. Which means that finally
> > the ASoC stuff can be made to build in mainline ... it was
> > probably sent to mainline before its time. ;)
> >
> > Following are three patches which resync mainline ASoC code
> > with what's in the DaVinci tree. I'd like to suggest they
> > all merge before 2.6.30-final ... two are build fixes, and
> > the third is needed to make it work.
>
> The patches haven't been sent yet?
I just cc'd Mark and Liam, maintainers of the ASoC stuff,
and the DaVinci list ...
http://linux.omap.com/pipermail/davinci-linux-open-source/2009-May/013339.html
http://linux.omap.com/pipermail/davinci-linux-open-source/2009-May/013338.html
http://linux.omap.com/pipermail/davinci-linux-open-source/2009-May/013340.html
If you want to merge them I'll forward those to you.
next prev parent reply other threads:[~2009-05-15 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 19:35 [patch 0/3] DaVinci ASoC updates David Brownell
2009-05-15 8:11 ` Takashi Iwai
2009-05-15 8:21 ` David Brownell [this message]
2009-05-15 8:22 ` Mark Brown
2009-05-15 8:32 ` Takashi Iwai
2009-05-15 8:19 ` Mark Brown
2009-05-15 8:52 ` David Brownell
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=200905150121.16736.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=tiwai@suse.de \
/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