Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753296AbZFEUtv (ORCPT ); Fri, 5 Jun 2009 16:49:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752093AbZFEUto (ORCPT ); Fri, 5 Jun 2009 16:49:44 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:36249 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751005AbZFEUtn (ORCPT ); Fri, 5 Jun 2009 16:49:43 -0400 Date: Fri, 5 Jun 2009 21:48:06 +0100 From: Russell King To: Sam Ravnborg Cc: Jaswinder Singh Rajput , Ingo Molnar , Catalin Marinas , Andrew Morton , LKML , linux-arm-kernel@lists.arm.linux.org.uk Subject: Re: [PATCH 1/6] headers_check fix: arm, hwcap.h Message-ID: <20090605204805.GA22367@flint.arm.linux.org.uk> References: <1244118232.5172.26.camel@ht.satnam> <1244118476.5172.29.camel@ht.satnam> <20090604125306.GC24491@flint.arm.linux.org.uk> <20090604201649.GC13892@uranus.ravnborg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090604201649.GC13892@uranus.ravnborg.org> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1810 Lines: 46 On Thu, Jun 04, 2009 at 10:16:49PM +0200, Sam Ravnborg wrote: > On Thu, Jun 04, 2009 at 01:53:07PM +0100, Russell King wrote: > > On Thu, Jun 04, 2009 at 05:57:56PM +0530, Jaswinder Singh Rajput wrote: > > > fix the following 'make headers_check' warning: > > > > I think headers_check needs fixing - there's nothing wrong with the > > code as it presently stands except the tools obviously can't properly > > parse C preprocessor statements. > > You are correct that headers_ceck is limited here and this patch > take some valid code and refactor it to make it headers_check compatible. Okay, here's the question: Does userspace require anything in the ifdef __ASSEMBLY__ bits? In any case, passing -D__KERNEL__ or -U__KERNEL__ allows unifdef to do the right thing. The problem which unifdef has is that if it finds a symbol in an evaluation that it doesn't know about, it fails the expansion entirely, rather than checking whether the expansion always results in something which should be omitted. In other words: #if defined(__KERNEL__) && () results in basically an "unknown" answer from the evaluator, where we can see perfectly well that the expansion can never be true if __KERNEL__ is never set. So, the trivial answer to the problem if: #if defined(__KERNEL__) && something-depending-on-__ASSEMBLY__ is to tell unifdef whether we want __ASSEMBLY__ defined or not defined. This does shut up the headers_install warning from ARMs hwdef.h. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: -- 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/