qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] cpu-defs.h: pull in qemu-common.h for HOST_LONG_BITS
Date: Mon, 16 Jul 2012 07:26:50 +0200	[thread overview]
Message-ID: <5003A61A.7080500@weilnetz.de> (raw)
In-Reply-To: <201207151754.08786.vapier@gentoo.org>

Am 15.07.2012 23:54, schrieb Mike Frysinger:
> On Sunday 15 July 2012 15:34:33 Stefan Weil wrote:
>> Am 15.07.2012 22:25, schrieb Mike Frysinger:
>>> This file uses the define HOST_LONG_BITS, but doesn't explicitly include
>>> qemu-common.h for it leading to build warnings for some setups:
>>> In file included from qemu/target-bfin/cpu.h:17,
>>>
>>>                    from qemu/cputlb.c:21:
>>> qemu/cpu-defs.h:83:5: warning: "HOST_LONG_BITS" is not defined
>>>
>>> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
>>> ---
>>>
>>>    cpu-defs.h |    1 +
>>>    1 file changed, 1 insertion(+)
>>>
>>> diff --git a/cpu-defs.h b/cpu-defs.h
>>> index f49e950..0d6018d 100644
>>> --- a/cpu-defs.h
>>> +++ b/cpu-defs.h
>>> @@ -28,6 +28,7 @@
>>>
>>>    #include <inttypes.h>
>>>    #include <signal.h>
>>>    #include "osdep.h"
>>>
>>> +#include "qemu-common.h"
>>>
>>>    #include "qemu-queue.h"
>>>    #include "targphys.h"
>> No. Of course this works, but I don't think that it is reasonable
>> to include qemu-common.h in every *.h file. There are already too
>> many of them.
>>
>> target-bfin/cpu.h should start like all other cpu.h files with
>> these include statements:
> sorry, but that's fragile junk.  if a header file uses defines from another
> header file, it should be including it.
> -mike

There are different ways how things can be done.

Normally, I agree with you that each header file should be complete,
but that's not the QEMU style.

In your special case, it's more important to keep all */cpu.h similar.
qemu/target-bfin/cpu.h is still not part of the official QEMU code,
so it can be fixed before it is committed.

Cheers,

Stefan

  reply	other threads:[~2012-07-16  5:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15 20:25 [Qemu-devel] [PATCH] cpu-defs.h: pull in qemu-common.h for HOST_LONG_BITS Mike Frysinger
2012-07-15 19:34 ` Stefan Weil
2012-07-15 21:54   ` Mike Frysinger
2012-07-16  5:26     ` Stefan Weil [this message]
2012-07-16  6:01       ` Stefan Weil
2012-07-18 12:13       ` Mike Frysinger
2012-07-18 13:14         ` Andreas Färber

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=5003A61A.7080500@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=qemu-devel@nongnu.org \
    --cc=vapier@gentoo.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).