qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Cc: "C.W. Betts" <computers57@hotmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sheepdog: fix compile error on systems without TCP_CORK
Date: Wed, 7 Jul 2010 19:42:50 +0000	[thread overview]
Message-ID: <AANLkTim49r31rIWWoJQZlsJPT93FZzZxj-v0_UGv_gmP@mail.gmail.com> (raw)
In-Reply-To: <1278483930-16479-1-git-send-email-morita.kazutaka@lab.ntt.co.jp>

Thanks, applied. It also fixes OpenBSD build.

On Wed, Jul 7, 2010 at 6:25 AM, MORITA Kazutaka
<morita.kazutaka@lab.ntt.co.jp> wrote:
> WIN32 is not only the system which doesn't have TCP_CORK (e.g. OS X).
>
> Signed-off-by: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
> ---
>
> Betts, I think this patch fix the compile error.  Can you try this
> one?
>
>  block/sheepdog.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/block/sheepdog.c b/block/sheepdog.c
> index 69a2494..81aa564 100644
> --- a/block/sheepdog.c
> +++ b/block/sheepdog.c
> @@ -889,7 +889,7 @@ static int aio_flush_request(void *opaque)
>     return !QLIST_EMPTY(&s->outstanding_aio_head);
>  }
>
> -#ifdef _WIN32
> +#if !defined(SOL_TCP) || !defined(TCP_CORK)
>
>  static int set_cork(int fd, int v)
>  {
> --
> 1.5.6.5
>
>
>

      parent reply	other threads:[~2010-07-07 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09  1:37 [Qemu-devel] don't look for libuuid on Darwin C.W. Betts
2009-11-09 14:11 ` Christoph Hellwig
     [not found]   ` <BLU0-SMTP7451A9F3D890AB80A8B4D9B9AC0@phx.gbl>
     [not found]     ` <20091109192221.GA28249@lst.de>
2009-11-10  4:29       ` C.W. Betts
2010-07-07  6:25 ` [Qemu-devel] [PATCH] sheepdog: fix compile error on systems without TCP_CORK MORITA Kazutaka
2010-07-07 16:32   ` C.W. Betts
2010-07-07 19:42   ` 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=AANLkTim49r31rIWWoJQZlsJPT93FZzZxj-v0_UGv_gmP@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=computers57@hotmail.com \
    --cc=morita.kazutaka@lab.ntt.co.jp \
    --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).