alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: OMAP: Kconfig string cleanup
Date: Tue, 13 Dec 2011 11:52:48 +0200	[thread overview]
Message-ID: <4EE72070.2050806@ti.com> (raw)
In-Reply-To: <20111213083119.GJ7148@opensource.wolfsonmicro.com>

On 12/13/2011 10:31 AM, Mark Brown wrote:
> On Tue, Dec 13, 2011 at 10:30:17AM +0200, Peter Ujfalusi wrote:
> 
>> -	tristate "SoC Audio for the Texas Instruments OMAP chips"
>> +	tristate "SoC Audio for Texas Instruments OMAP based boards"
>>  	depends on ARCH_OMAP
> 
>> -	tristate "SoC Audio support for Nokia N810"
>> +	tristate "Audio support for Nokia N810"
> 
> You should probably make your mind up if it's SoC audio or just plain
> audio.  I don't mind which, I just noticed the variation.

Initially I dropped the "Soc Audio" from the ASoC machine driver support
selection leaving only "Support for...".
Then I looked at for example Samsung's Kconfig. The most recent machine
config entries were using "Audio support for..." (9b8dc66f, 22cb839b,
abda5dfd, 0a590b1d) instead of the previously used "SoC PCM, I2S, S/PDIF
Audio Support for..."

Just ignore this patch. It is only cosmetic.

-- 
Péter

      reply	other threads:[~2011-12-13  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13  8:30 [PATCH] ASoC: OMAP: Kconfig string cleanup Peter Ujfalusi
2011-12-13  8:31 ` Mark Brown
2011-12-13  9:52   ` Peter Ujfalusi [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=4EE72070.2050806@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.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).