From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Hogan Subject: Re: [arc-linux-dev] Re: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches) Date: Wed, 14 Nov 2012 13:01:27 +0000 Message-ID: <50A39627.6020809@imgtec.com> References: <50A0D634.20005@synopsys.com> <509251CA.8050008@synopsys.com> <18137.1349203013@warthog.procyon.org.uk> ,<8419.1352387261@warthog.procyon.org.uk> <14356.1352416788@warthog.procyon.org.uk> <9377.1352726040@warthog.procyon.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from multi.imgtec.com ([194.200.65.239]:51627 "EHLO multi.imgtec.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422711Ab2KNNBa (ORCPT ); Wed, 14 Nov 2012 08:01:30 -0500 In-Reply-To: <9377.1352726040@warthog.procyon.org.uk> Sender: linux-arch-owner@vger.kernel.org List-ID: To: David Howells Cc: Vineet Gupta , "arnd@arndb.de" , "linux-arch@vger.kernel.org" , "linux-kernel@vger.kernel.org" Hi David, The disintegration scripts strip out the #ifdef __KERNEL__ from the headers in both uapi/ and the old directories. However there are still a bunch of unexported headers through the tree which have #ifdef __KERNEL__ in them, usually guarding the entire file (just grep __KERNEL__ in arch/). Is this something that you're already planning to eliminate? We have a few in the metag tree too, and now that uapi/ is nicely separated I'm not sure if it's worth removing the __KERNEL__ guards or keeping them to match other architectures. Thanks James