All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: David Brownell <david-b@pacbell.net>
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 16:18:47 +0100	[thread overview]
Message-ID: <20081003151846.GA9127@sirena.org.uk> (raw)
In-Reply-To: <200810030811.33484.david-b@pacbell.net>

On Fri, Oct 03, 2008 at 08:11:33AM -0700, David Brownell wrote:

> Get rid of bogus ASOC boot messages on non-Overo boards,
> such as with a kernel built for both Overo and Beagle.

<nitpick>It's ASoC, not ASOC.</nitpick>

> ---
> 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.  The change
looks good, FWIW but...

> @@ -135,13 +135,12 @@ err1:
>  
>  	return ret;
>  }
> +module_init(overo_soc_init);
>  
>  static void __exit overo_soc_exit(void)
>  {
>  	platform_device_unregister(overo_snd_device);
>  }
> -
> -module_init(overo_soc_init);
>  module_exit(overo_soc_exit);

This is a reasonable change but unrelated to your patch description.

  reply	other threads:[~2008-10-03 15:18 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 ` Mark Brown [this message]
2008-10-03 15:37   ` [alsa-devel] " David Brownell
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=20081003151846.GA9127@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=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.