Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966040AbXEVRrS (ORCPT ); Tue, 22 May 2007 13:47:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758711AbXEVRrI (ORCPT ); Tue, 22 May 2007 13:47:08 -0400 Received: from ug-out-1314.google.com ([66.249.92.168]:3801 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758169AbXEVRrF (ORCPT ); Tue, 22 May 2007 13:47:05 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cAm5GXJ+HjQuBqCBmpbhvuvUiYCnhrk4LpqVG/QA8gs0xeoTSxZhtbiUEckTWbAHj2zbjctagasMYlR1zwTAGiKed8P+Fk8ivjG7yzOXeJ9ftma6dKpZOn44N26pEinSL1KAaD3scDjMq+j+r7X+MB97u94t3NE45D2MwL/ym7s= Message-ID: Date: Tue, 22 May 2007 23:16:59 +0530 From: "Satyam Sharma" To: "Stefan Richter" Subject: Re: RFC: kconfig select warnings bogus? Cc: LKML , "Roman Zippel" , "Kumar Gala" , "Simon Horman" , "Adrian Bunk" , "Sam Ravnborg" In-Reply-To: <46532AA4.6080501@s5r6.in-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070519151523.GA26724@uranus.ravnborg.org> <46503542.50300@s5r6.in-berlin.de> <46504876.9040802@s5r6.in-berlin.de> <46505DBD.5010005@s5r6.in-berlin.de> <46532247.6030803@s5r6.in-berlin.de> <46532AA4.6080501@s5r6.in-berlin.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1475 Lines: 34 On 5/22/07, Stefan Richter wrote: > Satyam Sharma wrote: > > On 5/22/07, Stefan Richter wrote: > >> >> > On 5/20/07, Stefan Richter wrote: > >> >> >> depends on !PLATFORM_X || HELPER_N_ON_PLATFORM_X > ... > >> This is a synthetic example which might not have a real-world application.] > > > > Well, it is not relevant / equivalent to any of the four symbols that caused the > > warnings that this thread is about, at least. > > (Have I ever said that this concrete expression can be used in whatever > fix?) > > ... > > and as I said, this was totally *not* the problem being discussed / > > solved in this thread (and by that patch). > > My point was not about that particular expression. My point was: > > I'm not advocating any specific fixes or pseudo-fixes. > I'm advocating the notation of dependencies in the direction > "A requires B". > > When I said "The standard and maintainable way (for drivers at least) > is..." I didn't mean the example expression, I meant the *direction* in > which the example was stating dependencies. In that case I wish "the points" you make on threads are relevant to them. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/