From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, imp@bsdimp.com, kevans@freebsd.org,
ben.widawsky@intel.com, jonathan.cameron@huawei.com,
kbastian@mail.uni-paderborn.de, jasowang@redhat.com,
michael.roth@amd.com, kkostiuk@redhat.com, tsimpson@quicinc.com,
palmer@dabbelt.com, alistair.francis@wdc.com,
bin.meng@windriver.com, qemu-riscv@nongnu.org, philmd@linaro.org,
Bin Meng <bmeng.cn@gmail.com>
Subject: Re: [PATCH v3 1/1] include: Don't include qemu/osdep.h
Date: Thu, 12 Jan 2023 14:52:48 +0000 [thread overview]
Message-ID: <Y8AewFAHRGf6ZI3x@redhat.com> (raw)
In-Reply-To: <20230112082537-mutt-send-email-mst@kernel.org>
On Thu, Jan 12, 2023 at 08:51:26AM -0500, Michael S. Tsirkin wrote:
> On Thu, Jan 12, 2023 at 12:50:05PM +0100, Markus Armbruster wrote:
> > docs/devel/style.rst mandates:
> >
> > 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.
> >
> > A few violations have crept in. Fix them.
> >
> > Signed-off-by: Markus Armbruster <armbru@redhat.com>
> > Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> > Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
> > Reviewed-by: Taylor Simpson <tsimpson@quicinc.com>
> > Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
>
> With my awesome grep skillz I found one more:
> $ grep -r --include='*.h' qemu/osdep.h
> include/block/graph-lock.h:#include "qemu/osdep.h"
>
> Looks like all C files must include qemu/osdep.h, no?
Yes, and IMHO that is/was a mistake, as it means our other header
files are not self-contained, which prevents developer tools from
reporting useful bugs when you're editting.
For example, if you have clangd integrated into your editor, it will
warn you as you're editting if you've referenced a function / type
that doesn't exist in the file, or anything it includes. This is made
completely useless for QEMU .h files though, as they're all incomplete,
only the .c files have the full headers.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-01-12 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 11:50 [PATCH v3 0/1] Clean up includes Markus Armbruster
2023-01-12 11:50 ` [PATCH v3 1/1] include: Don't include qemu/osdep.h Markus Armbruster
2023-01-12 13:51 ` Michael S. Tsirkin
2023-01-12 13:56 ` Michael S. Tsirkin
2023-01-12 14:47 ` Markus Armbruster
2023-01-12 17:37 ` Michael S. Tsirkin
2023-01-12 17:44 ` Daniel P. Berrangé
2023-01-12 17:47 ` Michael S. Tsirkin
2023-01-12 14:52 ` Daniel P. Berrangé [this message]
2023-01-12 15:58 ` Peter Maydell
2023-01-12 16:07 ` Daniel P. Berrangé
2023-01-12 16:20 ` Peter Maydell
2023-01-12 16:30 ` Daniel P. Berrangé
2023-01-12 16:38 ` Peter Maydell
2023-01-12 17:43 ` Michael S. Tsirkin
2023-01-12 17:30 ` Jonathan Cameron via
2023-01-12 17:41 ` Michael S. Tsirkin
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=Y8AewFAHRGf6ZI3x@redhat.com \
--to=berrange@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=armbru@redhat.com \
--cc=ben.widawsky@intel.com \
--cc=bin.meng@windriver.com \
--cc=bmeng.cn@gmail.com \
--cc=imp@bsdimp.com \
--cc=jasowang@redhat.com \
--cc=jonathan.cameron@huawei.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=kevans@freebsd.org \
--cc=kkostiuk@redhat.com \
--cc=michael.roth@amd.com \
--cc=mst@redhat.com \
--cc=palmer@dabbelt.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=tsimpson@quicinc.com \
/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).