All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: AlexChen <alex.chen@huawei.com>
Cc: Thomas Huth <thuth@redhat.com>,  <lvivier@redhat.com>,
	 Paolo Bonzini <pbonzini@redhat.com>,
	 QEMU Trivial <qemu-trivial@nongnu.org>,
	 QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH V2] qtest: Fix bad printf format specifiers
Date: Fri, 06 Nov 2020 07:36:42 +0100	[thread overview]
Message-ID: <87sg9nouth.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <5FA3A0C6.5040500@huawei.com> (AlexChen's message of "Thu, 5 Nov 2020 14:50:46 +0800")

AlexChen <alex.chen@huawei.com> writes:

> We should use printf format specifier PRIu32 instead of "%d" for
> argument of type 'uint32_t'.

I prefer v1, which uses %u.

[...]



WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: AlexChen <alex.chen@huawei.com>
Cc: lvivier@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
	Thomas Huth <thuth@redhat.com>,
	QEMU Trivial <qemu-trivial@nongnu.org>,
	QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH V2] qtest: Fix bad printf format specifiers
Date: Fri, 06 Nov 2020 07:36:42 +0100	[thread overview]
Message-ID: <87sg9nouth.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <5FA3A0C6.5040500@huawei.com> (AlexChen's message of "Thu, 5 Nov 2020 14:50:46 +0800")

AlexChen <alex.chen@huawei.com> writes:

> We should use printf format specifier PRIu32 instead of "%d" for
> argument of type 'uint32_t'.

I prefer v1, which uses %u.

[...]



  parent reply	other threads:[~2020-11-06  6:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05  6:50 [PATCH V2] qtest: Fix bad printf format specifiers AlexChen
2020-11-05  6:50 ` AlexChen
2020-11-05  7:54 ` Thomas Huth
2020-11-05  7:54   ` Thomas Huth
2020-11-06  6:36 ` Markus Armbruster [this message]
2020-11-06  6:36   ` Markus Armbruster

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=87sg9nouth.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alex.chen@huawei.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.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 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.