From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] Cleanups around qemu-common.h
Date: Fri, 07 Jun 2019 17:21:38 +0200 [thread overview]
Message-ID: <874l51a0al.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20190523143508.25387-1-armbru@redhat.com> (Markus Armbruster's message of "Thu, 23 May 2019 16:35:04 +0200")
Markus Armbruster <armbru@redhat.com> writes:
> qemu-common.h stipulates:
>
> * If a header file uses a definition from qemu-common.h, that definition
> * must be moved to a separate header file, and the header that uses it
> * must include that header.
>
> I count 117 violations of that rule. This series fixes them. It also
> reduces the number of objects depending on qemu-common.h in my
> "everything" build from roughly 5800 out of 6500 to less than 600.
>
> I used my "[RFC v4 0/7] Baby steps towards saner headers" to check
> properly self-contained headers remain self-contained.
Queued.
prev parent reply other threads:[~2019-06-07 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 14:35 [Qemu-devel] [PATCH 0/4] Cleanups around qemu-common.h Markus Armbruster
2019-05-23 14:35 ` [Qemu-devel] [PATCH 1/4] qemu-common: Move tcg_enabled() etc. to sysemu/tcg.h Markus Armbruster
2019-05-23 18:38 ` Richard Henderson
2019-05-23 14:35 ` [Qemu-devel] [PATCH 2/4] qemu-common: Move qemu_isalnum() etc. to qemu/ctype.h Markus Armbruster
2019-05-23 18:39 ` Richard Henderson
2019-05-23 14:35 ` [Qemu-devel] [PATCH 3/4] Include qemu/module.h where needed, drop it from qemu-common.h Markus Armbruster
2019-05-23 14:35 ` [Qemu-devel] [PATCH 4/4] Include qemu-common.h exactly where needed Markus Armbruster
2019-06-07 15:21 ` Markus Armbruster [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=874l51a0al.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--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).