From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=53439 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OHat8-0002iZ-8b for qemu-devel@nongnu.org; Thu, 27 May 2010 07:04:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OHat6-0007vJ-C8 for qemu-devel@nongnu.org; Thu, 27 May 2010 07:04:34 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59111) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OHat6-0007vA-5p for qemu-devel@nongnu.org; Thu, 27 May 2010 07:04:32 -0400 Message-ID: <4BFE51BB.1020408@redhat.com> Date: Thu, 27 May 2010 13:04:27 +0200 From: Jes Sorensen MIME-Version: 1.0 References: <1274955749-20689-1-git-send-email-Jes.Sorensen@redhat.com> <20100527104414.GA7250@redhat.com> <4BFE4FB5.5000300@redhat.com> <20100527105424.GA7376@redhat.com> In-Reply-To: <20100527105424.GA7376@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH] vhost_net.c: v2 Fix build failure introduced by 0bfcd599e3f5c5679cc7d0165a0a1822e2f60de2 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org On 05/27/10 12:54, Michael S. Tsirkin wrote: > On Thu, May 27, 2010 at 12:55:49PM +0200, Jes Sorensen wrote: >> On 05/27/10 12:44, Michael S. Tsirkin wrote: >>> On Thu, May 27, 2010 at 12:22:29PM +0200, Jes.Sorensen@redhat.com wrote: >>>> From: Jes Sorensen >>>> >>>> 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 >>> >>> I think this part of 0bfcd599e3f5c5679cc7d0165a0a1822e2f60de2 >>> should just be reverted. We have unsigned long, it should be printed >>> woith %ll. Casting to uint64_t just so we can print with PRIu64 seems silly. >> >> That is an option too. > > More importantly does this fix the problem for you? Yes it works fine. Acked-by: Jes Sorensen