public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Alsa-devel] [2.6 patch] let SND_SUPPORT_OLD_API depend on SND_PCM
Date: Tue, 10 Jan 2006 18:08:36 +0100	[thread overview]
Message-ID: <20060110170836.GP3911@stusta.de> (raw)
In-Reply-To: <s5hmzi4f26q.wl%tiwai@suse.de>

On Tue, Jan 10, 2006 at 06:00:29PM +0100, Takashi Iwai wrote:
> At Tue, 10 Jan 2006 17:44:49 +0100,
> Adrian Bunk wrote:
> > 
> > SND_SUPPORT_OLD_API only has an effect if SND_PCM is set.
> > 
> > 
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> > 
> > --- linux-2.6.15-mm2-full/sound/core/Kconfig.old	2006-01-10 17:35:35.000000000 +0100
> > +++ linux-2.6.15-mm2-full/sound/core/Kconfig	2006-01-10 17:36:07.000000000 +0100
> > @@ -124,7 +124,7 @@
> >  
> >  config SND_SUPPORT_OLD_API
> >  	bool "Support old ALSA API"
> > -	depends on SND
> > +	depends on SND_PCM
> >  	default y
> >  	help
> >  	  Say Y here to support the obsolete ALSA PCM API (ver.0.9.0 rc3
> 
> Does it work?  CONFIG_SND_PCM is selected by the drivers.  So, it will
> be N until any drivers are selected.

It does work and "make oldconfig" handles it perfectly, but I understand 
your point that it might be accidentially set to N if a user later 
selects a driver in "make {menu,x}oldconfig", and that this case is most 
likely better handled without my patch.

> Takashi

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-01-10 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10 16:44 [2.6 patch] let SND_SUPPORT_OLD_API depend on SND_PCM Adrian Bunk
2006-01-10 17:00 ` [Alsa-devel] " Takashi Iwai
2006-01-10 17:08   ` Adrian Bunk [this message]
2006-01-10 17:39     ` Takashi Iwai

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=20060110170836.GP3911@stusta.de \
    --to=bunk@stusta.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --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