From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id CB8C9711 for ; Wed, 6 Aug 2014 16:24:28 +0000 (UTC) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5722F201A9 for ; Wed, 6 Aug 2014 16:24:28 +0000 (UTC) From: David Howells In-Reply-To: <20140806144519.GB14247@kroah.com> References: <20140806144519.GB14247@kroah.com> <18667.1407324523@warthog.procyon.org.uk> To: Greg KH MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <21296.1407342261.1@warthog.procyon.org.uk> Date: Wed, 06 Aug 2014 17:24:21 +0100 Message-ID: <21297.1407342261@warthog.procyon.org.uk> Cc: Jamal Hadi Salim , ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] Should .c files be discouraged from #including UAPI headers directly? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Greg KH wrote: > Why does it matter? What works "better" if a .c file doesn't include > the uapi.h file? Some of the UAPI headers are 'fixed up' by the non-UAPI header. In linux/types.h, for example: #define __EXPORTED_HEADERS__ #include and linux/acct.h: #include ... #undef ACCT_VERSION #undef AHZ and linux/quota.h: #include ... #undef USRQUOTA #undef GRPQUOTA I don't now remember where they all are:-/ David