From: David Howells <dhowells@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Should .c files be discouraged from #including UAPI headers directly?
Date: Wed, 06 Aug 2014 17:24:21 +0100 [thread overview]
Message-ID: <21297.1407342261@warthog.procyon.org.uk> (raw)
In-Reply-To: <20140806144519.GB14247@kroah.com>
Greg KH <greg@kroah.com> 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 <uapi/linux/types.h>
and linux/acct.h:
#include <uapi/linux/acct.h>
...
#undef ACCT_VERSION
#undef AHZ
and linux/quota.h:
#include <uapi/linux/quota.h>
...
#undef USRQUOTA
#undef GRPQUOTA
I don't now remember where they all are:-/
David
prev parent reply other threads:[~2014-08-06 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 11:28 David Howells
2014-08-06 14:45 ` Greg KH
2014-08-06 16:11 ` Jamal Hadi Salim
2014-08-06 16:24 ` David Howells [this message]
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=21297.1407342261@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=greg@kroah.com \
--cc=jhs@mojatatu.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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