All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC: use of qemu-common.h include
Date: Fri, 31 Jul 2015 13:30:21 +0100	[thread overview]
Message-ID: <20150731123021.GH2392@redhat.com> (raw)
In-Reply-To: <CAFEAcA-kJwhj4m7YOD8vxQrpP+Ap6MEmAartyQoX7sxS=u+Jiw@mail.gmail.com>

On Fri, Jul 31, 2015 at 01:19:11PM +0100, Peter Maydell wrote:
> On 31 July 2015 at 13:06, Daniel P. Berrange <berrange@redhat.com> wrote:
> > In fixing the mingw64 problem wrt to localtime_r availability, I relied
> > on the fact that qemu-common.h is supposed to be included everywhere,
> > to guarantee that we always have unistd.h included before time.h:
> 
> It's not really supposed to be included everywhere. It's just a
> convenient way for a .c file to get a lot of stuff all at once.
> It's a bit of a mess.
> 
> > So I'm wondering if there is appetite for cleaning this and and
> > introducing standard practice for inclusion of qemu-common.h ?
> 
> You might want to have a look at my series which tries to
> make osdep.h the "anybody can include this to get the really
> key 'breaks if this isn't here' stuff".
> 
> http://lists.nongnu.org/archive/html/qemu-devel/2015-07/msg04593.html

Ah, interesting, I'll check out that series - it sounds like it is
similar to what i was thinking

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

      reply	other threads:[~2015-07-31 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 12:06 [Qemu-devel] RFC: use of qemu-common.h include Daniel P. Berrange
2015-07-31 12:19 ` Peter Maydell
2015-07-31 12:30   ` Daniel P. Berrange [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=20150731123021.GH2392@redhat.com \
    --to=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.