From: Takashi Iwai <tiwai@suse.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Uwe Bugla <uwe.bugla@gmx.de>,
linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@suse.cz>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: BUG in 2.6.22-rc2-mm1: Parts of Alsa sound architecture broken
Date: Tue, 29 May 2007 18:41:13 +0200 [thread overview]
Message-ID: <s5hveebziom.wl%tiwai@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0705261248150.7344@yvahk01.tjqt.qr>
At Sat, 26 May 2007 12:51:48 +0200 (MEST),
Jan Engelhardt wrote:
>
>
> On May 25 2007 23:33, Takashi Iwai wrote:
> >
> >Yeah, I'll check it again if reposted. Jan, could you split ALSA
> >portins at the next time?
>
> How much split? This time, I made four out of it.
Thanks, that's enough and helpful. It was just becuase currently we
have a HG tree containing only ALSA portion and a git tree for the
merge, and above all, because I have no control over the latter git
tree...
> >This will make testing and merging much
> >easier for me...
> >
> >But, above all, I'm not convinced much by that patch, especially
> >because it introduces new kconfigs just for menuconfig.
> >For example, CONFIG_SND_PCI_DRIVERS doesn't appear in any Makefiles.
>
> Neither is/was CONFIG_DVB IIRC. The world does not stop turning just
> because there are now extra options. If you want the functionality
> of menuconfigs without introducing some variable to store their state,
> well, I think that's going to be a bigger kconf patch. (Just think of
> compatibility of the .config format.)
Well, I find the change of CONFIG_SND to menuconfig is fine, too.
But CONFIG_SND_PCI_DRIVERS and others don't make much sense to me.
How is it useful at all?
Anyway, I'd like to confirm that this really works before merging to
the ALSA tree. As Mauro suspected, kconfig seems not working as
expected...
thanks,
Takashi
next prev parent reply other threads:[~2007-05-29 16:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 20:00 BUG in 2.6.22-rc2-mm1: Parts of Alsa sound architecture broken Uwe Bugla
2007-05-24 20:09 ` Andrew Morton
2007-05-24 20:23 ` Uwe Bugla
2007-05-25 16:01 ` Takashi Iwai
2007-05-25 17:28 ` Andrew Morton
2007-05-25 18:29 ` Uwe Bugla
2007-05-25 21:33 ` Takashi Iwai
2007-05-26 10:51 ` Jan Engelhardt
2007-05-26 14:38 ` Mauro Carvalho Chehab
2007-05-29 16:41 ` Takashi Iwai [this message]
2007-05-29 20:18 ` Jan Engelhardt
2007-05-29 20:39 ` Mauro Carvalho Chehab
2007-05-29 21:53 ` Jan Engelhardt
2007-06-05 12:26 ` Takashi Iwai
2007-06-05 12:50 ` Takashi Iwai
2007-06-05 13:25 ` Jan Engelhardt
2007-06-05 14:17 ` Takashi Iwai
2007-06-05 14:20 ` Jan Engelhardt
2007-06-05 14:31 ` Takashi Iwai
2007-06-06 19:36 ` Jens Axboe
2007-06-06 19:53 ` Sam Ravnborg
2007-06-08 9:29 ` Takashi Iwai
2007-05-26 10:39 ` Jan Engelhardt
2007-05-26 10:40 ` [PATCH 01/04] Use menuconfig objects 3 - sound Jan Engelhardt
2007-05-26 10:40 ` [PATCH 02/04] Use menuconfig objects 3 - sound/alsa Jan Engelhardt
2007-05-26 10:41 ` [PATCH 03/04] Use menuconfig objects 3 - sound/alsa/more Jan Engelhardt
2007-05-26 10:41 ` [PATCH 04/04] Use menuconfig objects 3 - sound/oss Jan Engelhardt
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=s5hveebziom.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=perex@suse.cz \
--cc=uwe.bugla@gmx.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