qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Fam Zheng <famz@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Eric Blake <eblake@redhat.com>
Subject: [Qemu-devel] [PULL 01/14] HACKING: document #include order
Date: Wed,  4 Jan 2017 13:34:01 +0000	[thread overview]
Message-ID: <20170104133414.6524-2-stefanha@redhat.com> (raw)
In-Reply-To: <20170104133414.6524-1-stefanha@redhat.com>

It was not obvious to me why "qemu/osdep.h" must be the first #include.
This documents the rationale and the overall #include order.

Cc: Fam Zheng <famz@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>
Cc: Eric Blake <eblake@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Message-id: 1479307161-24658-1-git-send-email-stefanha@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 HACKING | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/HACKING b/HACKING
index 20a9101..4125c97 100644
--- a/HACKING
+++ b/HACKING
@@ -1,10 +1,28 @@
 1. Preprocessor
 
+1.1. Variadic macros
+
 For variadic macros, stick with this C99-like syntax:
 
 #define DPRINTF(fmt, ...)                                       \
     do { printf("IRQ: " fmt, ## __VA_ARGS__); } while (0)
 
+1.2. Include directives
+
+Order include directives as follows:
+
+#include "qemu/osdep.h"  /* Always first... */
+#include <...>           /* then system headers... */
+#include "..."           /* and finally QEMU headers. */
+
+The "qemu/osdep.h" header contains preprocessor macros that affect the behavior
+of core system headers like <stdint.h>.  It must be the first include so that
+core system headers included by external libraries get the preprocessor macros
+that QEMU depends on.
+
+Do not include "qemu/osdep.h" from header files since the .c file will have
+already included it.
+
 2. C types
 
 It should be common sense to use the right type, but we have collected
-- 
2.9.3

  reply	other threads:[~2017-01-04 13:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 13:34 [Qemu-devel] [PULL 00/14] Block patches Stefan Hajnoczi
2017-01-04 13:34 ` Stefan Hajnoczi [this message]
2017-01-04 13:34 ` [Qemu-devel] [PULL 02/14] aio: add flag to skip fds to aio_dispatch() Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 03/14] aio: add AioPollFn and io_poll() interface Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 04/14] aio: add polling mode to AioContext Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 05/14] virtio: poll virtqueues for new buffers Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 06/14] linux-aio: poll ring for completions Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 07/14] iothread: add polling parameters Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 08/14] virtio-blk: suppress virtqueue kick during processing Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 09/14] virtio-scsi: " Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 10/14] virtio: turn vq->notification into a nested counter Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 11/14] aio: add .io_poll_begin/end() callbacks Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 12/14] virtio: disable virtqueue notifications during polling Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 13/14] aio: self-tune polling time Stefan Hajnoczi
2017-01-04 13:34 ` [Qemu-devel] [PULL 14/14] iothread: add poll-grow and poll-shrink parameters Stefan Hajnoczi
2017-01-05 13:57 ` [Qemu-devel] [PULL 00/14] Block patches Peter Maydell

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=20170104133414.6524-2-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=famz@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).