qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Error: Fix build when qemu-common.h is not included
Date: Thu, 07 Jul 2011 18:50:28 +0200	[thread overview]
Message-ID: <4E15E3D4.6020701@mail.berlios.de> (raw)
In-Reply-To: <4E15DC0B.7050608@linux.vnet.ibm.com>

Am 07.07.2011 18:17, schrieb Michael Roth:
> On 07/07/2011 11:02 AM, Luiz Capitulino wrote:
>> Commit e4ea5e2d0e0e4c5188ab45b66f3195062ae059dc added the use of
>> the macro GCC_FMT_ATTR to error.h, however qemu-common.h is not
>> included by error.h
>>
>> This will cause a build error when files including error.h
>> don't include qemu-common.h. Not an issue today because the only
>> file including it is json-parser.h and it does include
>> qemu-common.h, but let's fix it.
>>
>> Signed-off-by: Luiz Capitulino<lcapitulino@redhat.com>
>> ---
>>   error.h |    2 +-
>>   1 files changed, 1 insertions(+), 1 deletions(-)

The same argument could be applied to more QEMU *.h files
which also work only after qemu-common.h. Otherwise, including
qemu-common.h in *.c files would rarely be needed.

As far as I remember, the *.h files used to be more self-contained
some years ago, but then the strategy changed and central files
like qemu-common.h were introduced.

I personally prefer self-contained include files like error.h
(before my patch and after your patch), but I'm afraid that
the QEMU way is different.

Cheers,
Stefan W.

  reply	other threads:[~2011-07-07 17:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 16:02 [Qemu-devel] [PATCH] Error: Fix build when qemu-common.h is not included Luiz Capitulino
2011-07-07 16:17 ` Michael Roth
2011-07-07 16:50   ` Stefan Weil [this message]
2011-07-07 17:32     ` Luiz Capitulino

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=4E15E3D4.6020701@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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).