All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Jes.Sorensen@redhat.com
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vhost_net.c: Fix build failure introduced by	0bfcd599e3f5c5679cc7d0165a0a1822e2f60de2
Date: Thu, 27 May 2010 12:18:47 +0200	[thread overview]
Message-ID: <4BFE4707.3060501@redhat.com> (raw)
In-Reply-To: <1274954895-20460-1-git-send-email-Jes.Sorensen@redhat.com>

On 05/27/10 12:08, Jes.Sorensen@redhat.com wrote:
> From: Jes Sorensen <Jes.Sorensen@redhat.com>
> 
> Fix build failure introduced by 0bfcd599e3f5c5679cc7d0165a0a1822e2f60de2
> 
> The format statement expects unsigned long on x86_64, but receives
> unsigned long long, so gcc exits with an error.
> 
> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>

ARGH, sorry, this one was only half finished - please ignore. I'll post
a working version in a minute.

Jes

      reply	other threads:[~2010-05-27 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 10:08 [Qemu-devel] [PATCH] vhost_net.c: Fix build failure introduced by 0bfcd599e3f5c5679cc7d0165a0a1822e2f60de2 Jes.Sorensen
2010-05-27 10:18 ` Jes Sorensen [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=4BFE4707.3060501@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=blauwirbel@gmail.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 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.