From: Stefan Weil <sw@weilnetz.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 00/15] Clean some includes and definitions
Date: Thu, 2 Feb 2012 22:12:42 +0100 [thread overview]
Message-ID: <1328217177-32745-1-git-send-email-sw@weilnetz.de> (raw)
Hi,
I tried to move the definition of HOST_LONG_BITS from configure
to qemu-common.h. While doing this, I noticed that the different
QEMU targets use includes in non-uniform ways.
So the simple goal resulted in quite a lot of patches.
Patch 1 simply removes a derived macro. This patch is independent of
the others.
The next patches try to implement a more uniform include scheme
for the TCG targets than today:
* cpu.h always starts with config.h and qemu-common.h.
* config.h is not needed before cpu.h
* qemu-common.h is not needed after cpu.h.
* Standard includes are not needed because they are already in qemu-common.h
This also avoids potential errors when qemu-common.h is included without
a preceding config.h. Future code changes should be easier as soon as all
targets use a uniform include scheme.
The last patch finally achieves my initial goal.
Regards,
Stefan Weil
[PATCH 01/15] Remove macro HOST_LONG_SIZE
[PATCH 02/15] target-alpha: Clean includes
[PATCH 03/15] target-arm: Clean includes
[PATCH 04/15] target-cris: Clean includes
[PATCH 05/15] target-i386: Clean includes
[PATCH 06/15] target-lm32: Clean includes
[PATCH 07/15] target-m68k: Clean includes
[PATCH 08/15] target-microblaze: Clean includes
[PATCH 09/15] target-mips: Clean includes
[PATCH 10/15] target-ppc: Clean includes
[PATCH 11/15] target-s390x: Clean includes
[PATCH 12/15] target-sh4: Clean includes
[PATCH 13/15] target-unicore32: Clean includes
[PATCH 14/15] target-xtensa: Clean includes
[PATCH 15/15] Move definition of HOST_LONG_BITS to qemu-common.h
next reply other threads:[~2012-02-02 21:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 21:12 Stefan Weil [this message]
2012-02-02 21:12 ` [Qemu-devel] [PATCH 01/15] Remove macro HOST_LONG_SIZE Stefan Weil
2012-02-02 21:12 ` [Qemu-devel] [PATCH 02/15] target-alpha: Clean includes Stefan Weil
2012-02-02 21:12 ` [Qemu-devel] [PATCH 03/15] target-arm: " Stefan Weil
2012-02-02 23:22 ` Peter Maydell
2012-02-02 21:12 ` [Qemu-devel] [PATCH 04/15] target-cris: " Stefan Weil
2012-02-02 21:12 ` [Qemu-devel] [PATCH 05/15] target-i386: " Stefan Weil
2012-02-02 21:12 ` [Qemu-devel] [PATCH 06/15] target-lm32: " Stefan Weil
2012-02-04 14:50 ` Michael Walle
2012-02-02 21:12 ` [Qemu-devel] [PATCH 07/15] target-m68k: " Stefan Weil
2012-02-02 21:12 ` [Qemu-devel] [PATCH 08/15] target-microblaze: " Stefan Weil
2012-02-02 21:12 ` [Qemu-devel] [PATCH 09/15] target-mips: " Stefan Weil
2012-02-02 21:12 ` [Qemu-devel] [PATCH 10/15] target-ppc: " Stefan Weil
2012-02-02 21:26 ` Alexander Graf
2012-02-02 22:46 ` Stefan Weil
2012-02-02 22:51 ` Alexander Graf
2012-02-02 21:12 ` [Qemu-devel] [PATCH 11/15] target-s390x: " Stefan Weil
2012-02-02 21:12 ` [Qemu-devel] [PATCH 12/15] target-sh4: " Stefan Weil
2012-02-02 21:12 ` [Qemu-devel] [PATCH 13/15] target-unicore32: " Stefan Weil
2012-02-02 21:12 ` [Qemu-devel] [PATCH 14/15] target-xtensa: " Stefan Weil
2012-02-02 21:30 ` Max Filippov
2012-02-02 21:12 ` [Qemu-devel] [PATCH 15/15] Move definition of HOST_LONG_BITS to qemu-common.h Stefan Weil
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=1328217177-32745-1-git-send-email-sw@weilnetz.de \
--to=sw@weilnetz.de \
--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).