public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: [RFC/PATCH 0/1] ALSA SoC support for OMAP
Date: Fri, 4 Apr 2008 16:31:00 +0300	[thread overview]
Message-ID: <20080404163100.6d3090dc.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <20080404124233.GB23571@rakim.wolfsonmicro.main>

On Fri, 4 Apr 2008 13:42:33 +0100
"ext Mark Brown" <broonie@opensource.wolfsonmicro.com> wrote:

> On Fri, Apr 04, 2008 at 12:22:27PM +0300, Jarkko Nikula wrote:
> 
> > Here is the second version of ASoC support for OMAP. Now based to
> > dev branch of git://opensource.wolfsonmicro.com/linux-2.6-asoc but
> > applies to linux-omap by modifying Kconfig and Makefile in
> > sound/soc/.
> 
> Looks good from an ASoC point of view, thanks - I've applied the patch
> to the dev branch but won't push it anywhere for the time being.
>
Ok, I'll keep you informed when the include/asm-arm/arch-omap/control.h
is in and my omap-mcbsp.c compiles cleanly.

Currently the missing file it's in Russell's patch queue:

http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=4920/1


Jarkko

      reply	other threads:[~2008-04-04 13:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04  9:22 [RFC/PATCH 0/1] ALSA SoC support for OMAP Jarkko Nikula
2008-04-04  9:22 ` [RFC/PATCH 1/1] ASoC: Add drivers for the Texas Instruments OMAP processors Jarkko Nikula
2008-04-21 18:16   ` Tony Lindgren
2008-04-22  6:48     ` Jarkko Nikula
2008-04-22  8:49       ` Mark Brown
2008-04-23 23:59         ` [alsa-devel] " Tony Lindgren
2008-04-04 12:42 ` [RFC/PATCH 0/1] ALSA SoC support for OMAP Mark Brown
2008-04-04 13:31   ` Jarkko Nikula [this message]

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=20080404163100.6d3090dc.jarkko.nikula@nokia.com \
    --to=jarkko.nikula@nokia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox