qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Bihong Yu <yubihong@huawei.com>
Cc: alex.chen@huawei.com, Juan Quintela <quintela@redhat.com>,
	QEMU Trivial <qemu-trivial@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	zhengchuan@huawei.com, wanghao232@huawei.com
Subject: Re: [PATCH v1 2/8] migration: Don't use '#' flag of printf format
Date: Sun, 11 Oct 2020 19:19:15 +0100	[thread overview]
Message-ID: <CAFEAcA_VGzPsteNKjYkm7PGUn5As5Z+XWLMZq60ph055LqqfrA@mail.gmail.com> (raw)
In-Reply-To: <1602413863-19513-3-git-send-email-yubihong@huawei.com>

On Sun, 11 Oct 2020 at 14:52, Bihong Yu <yubihong@huawei.com> wrote:
> @@ -998,7 +998,7 @@ static int block_load(QEMUFile *f, void *opaque, int version_id)
>                     (addr == 100) ? '\n' : '\r');
>              fflush(stdout);
>          } else if (!(flags & BLK_MIG_FLAG_EOS)) {
> -            fprintf(stderr, "Unknown block migration flags: %#x\n", flags);
> +            fprintf(stderr, "Unknown block migration flags: %0x\n", flags);

This doesn't look right. "%#x" will print a number in hex with a leading '0x'.
To get the same effect without using "#" you need "0x%x" (that is,
the format string provides the 0x characters literally).
What you've written is '%0x", which is a format string where the '0' is
a request to print with zero padding (which is ignored since there's no
field width given), so the result is the same as if you'd just said '%x',
and there is no '0x' in the output.

$ cat /tmp/zz9.c
#include <stdio.h>
int main(void) {
  printf("%#x\n", 42);
  printf("%0x\n", 42);
  printf("0x%x\n", 42);
  return 0;
}
$ gcc -g -Wall -o /tmp/zz9 /tmp/zz9.c
$ /tmp/zz9
0x2a
2a
0x2a

>          default:
> -            error_report("Unknown combination of migration flags: %#x"
> +            error_report("Unknown combination of migration flags: %0x"
>                           " (postcopy mode)", flags);
>              ret = -EINVAL;
>              break;
> @@ -3576,7 +3576,7 @@ static int ram_load_precopy(QEMUFile *f)
>              if (flags & RAM_SAVE_FLAG_HOOK) {
>                  ram_control_load_hook(f, RAM_CONTROL_HOOK, NULL);
>              } else {
> -                error_report("Unknown combination of migration flags: %#x",
> +                error_report("Unknown combination of migration flags: %0x",
>                               flags);
>                  ret = -EINVAL;
>              }

These two similarly should be "0x%x".

thanks
-- PMM


  reply	other threads:[~2020-10-11 18:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11 10:57 [PATCH v1 0/8] Fix some style problems in migration Bihong Yu
2020-10-11 10:57 ` [PATCH v1 1/8] migration: Do not use C99 // comments Bihong Yu
2020-10-11 10:57 ` [PATCH v1 2/8] migration: Don't use '#' flag of printf format Bihong Yu
2020-10-11 18:19   ` Peter Maydell [this message]
2020-10-12 12:45     ` Bihong Yu
2020-10-11 10:57 ` [PATCH v1 3/8] migration: Add spaces around operator Bihong Yu
2020-10-11 10:57 ` [PATCH v1 4/8] migration: Open brace '{' following struct go on the same line Bihong Yu
2020-10-11 10:57 ` [PATCH v1 5/8] migration: Add braces {} for if statement Bihong Yu
2020-10-11 10:57 ` [PATCH v1 6/8] migration: Do not initialise statics and globals to 0 or NULL Bihong Yu
2020-10-11 10:57 ` [PATCH v1 7/8] migration: Open brace '{' following function declarations go on the next line Bihong Yu
2020-10-11 10:57 ` [PATCH v1 8/8] migration: Delete redundant spaces Bihong Yu
2020-10-11 14:48 ` [PATCH v1 0/8] Fix some style problems in migration no-reply
  -- strict thread matches above, loose matches on Subject: below --
2020-10-11 10:48 Bihong Yu
2020-10-11 10:48 ` [PATCH v1 2/8] migration: Don't use '#' flag of printf format Bihong Yu
2020-10-11 10:17 [PATCH v1 0/8] Fix some style problems in migration Bihong Yu
2020-10-11 10:17 ` [PATCH v1 2/8] migration: Don't use '#' flag of printf format Bihong Yu

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=CAFEAcA_VGzPsteNKjYkm7PGUn5As5Z+XWLMZq60ph055LqqfrA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=alex.chen@huawei.com \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=wanghao232@huawei.com \
    --cc=yubihong@huawei.com \
    --cc=zhengchuan@huawei.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).