qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [Commit 20d97356] Fix OpenBSD build
Date: Thu, 6 May 2010 20:55:06 +0300	[thread overview]
Message-ID: <x2kf43fc5581005061055pcb5e402dtbc078e4c21833283@mail.gmail.com> (raw)
In-Reply-To: <4BE129F0.8000905@redhat.com>

On 5/5/10, Kevin Wolf <kwolf@redhat.com> wrote:
> Hi Blue Swirl,
>
>  did I miss the patch posted for this commit? I can't find it on the
>  mailing list. I think the BlockDriver declarations should really stay at
>  the end of the source file of each driver.
>
>  What about using a different way to get rid of the static forward
>  declaration, namely using bdrv_find_format() instead of referencing it
>  directly? If you agree I'll post patches to revert your change and use
>  this solution instead.

Somehow I can't form in my mind the change from your description, but
I'd be fine with that too if it also compiles in OpenBSD.

      reply	other threads:[~2010-05-06 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05  8:18 [Qemu-devel] [Commit 20d97356] Fix OpenBSD build Kevin Wolf
2010-05-06 17:55 ` Blue Swirl [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=x2kf43fc5581005061055pcb5e402dtbc078e4c21833283@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=Qemu-devel@nongnu.org \
    --cc=kwolf@redhat.com \
    /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).