All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Peter Lemenkov <lemenkov@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/1] Fix compilation: format string - acb->sector_num is long long
Date: Wed, 22 Sep 2010 14:47:18 -0500	[thread overview]
Message-ID: <4C9A5D46.2050509@codemonkey.ws> (raw)
In-Reply-To: <1285184023-27762-1-git-send-email-lemenkov@gmail.com>

On 09/22/2010 02:33 PM, Peter Lemenkov wrote:
> Signed-off-by: Peter Lemenkov<lemenkov@gmail.com>
> ---
>   block/blkverify.c |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/block/blkverify.c b/block/blkverify.c
> index 4202685..033eab2 100644
> --- a/block/blkverify.c
> +++ b/block/blkverify.c
> @@ -58,7 +58,7 @@ static void blkverify_err(BlkverifyAIOCB *acb, const char *fmt, ...)
>       va_list ap;
>
>       va_start(ap, fmt);
> -    fprintf(stderr, "blkverify: %s sector_num=%ld nb_sectors=%d ",
> +    fprintf(stderr, "blkverify: %s sector_num=%lld nb_sectors=%d ",
>               acb->is_write ? "write" : "read", acb->sector_num,
>    

It's not a long long, it's a PRId64.  I've updated appropriately.

Regards,

Anthony Liguori

>               acb->nb_sectors);
>       vfprintf(stderr, fmt, ap);
>    

      parent reply	other threads:[~2010-09-22 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 19:33 [Qemu-devel] [PATCH 1/1] Fix compilation: format string - acb->sector_num is long long Peter Lemenkov
2010-09-22 19:44 ` Blue Swirl
2010-09-22 19:47 ` Anthony Liguori [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=4C9A5D46.2050509@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=lemenkov@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.