alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] Add Phytec i.MX sound support for AC97
Date: Wed, 10 Feb 2010 11:24:15 +0100	[thread overview]
Message-ID: <20100210102415.GO17643@pengutronix.de> (raw)
In-Reply-To: <20100209195322.GA13437@opensource.wolfsonmicro.com>

On Tue, Feb 09, 2010 at 07:53:22PM +0000, Mark Brown wrote:
> On Tue, Feb 09, 2010 at 11:14:28AM +0100, Sascha Hauer wrote:
> 
> >  config SND_IMX_SOC
> >  	tristate "SoC Audio for Freecale i.MX CPUs"
> > -	depends on ARCH_MXC && BROKEN
> > +	depends on ARCH_MXC
> 
> BTW, this should not be here - we still need to wait for the arch/arm
> side of things to merge in before the drivers will work.

I added the corresponding files to my mxc-master branch and they should
show up on -next tomorrow. I removed the BROKEN in this patch because I
was sure that I add the files during this merge window and because it
shouldn't cause compile breakage in the mean time since the driver is
not selected in any config. But of course you are right, will do so
next time.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2010-02-10 10:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 10:14 [PATCH] Add Phytec i.MX sound support for AC97 Sascha Hauer
2010-02-09 10:42 ` Liam Girdwood
2010-02-09 11:37 ` Mark Brown
2010-02-09 19:53 ` Mark Brown
2010-02-10 10:24   ` Sascha Hauer [this message]
2010-02-10 10:51     ` Mark Brown

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=20100210102415.GO17643@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).