From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: peterx@redhat.com, qemu-devel@nongnu.org
Cc: Prasad Pandit <ppandit@redhat.com>,
Fabiano Rosas <farosas@suse.de>, Bandan Das <bdas@redhat.com>,
Julia Suvorova <jusual@redhat.com>
Subject: Re: [PATCH 1/3] migration: Make threshold_size an uint64_t
Date: Wed, 17 Jan 2024 09:09:27 +0100 [thread overview]
Message-ID: <b91f763a-3d06-45aa-97af-3971e843514b@linaro.org> (raw)
In-Reply-To: <20240117075848.139045-2-peterx@redhat.com>
On 17/1/24 08:58, peterx@redhat.com wrote:
> From: Peter Xu <peterx@redhat.com>
>
> It's always used to compare against another uint64_t. Make it always clear
> that it's never a negative.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
> migration/migration.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2024-01-17 8:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 7:58 [PATCH 0/3] migration: some small cleanups peterx
2024-01-17 7:58 ` [PATCH 1/3] migration: Make threshold_size an uint64_t peterx
2024-01-17 8:09 ` Philippe Mathieu-Daudé [this message]
2024-01-19 13:26 ` Fabiano Rosas
2024-01-17 7:58 ` [PATCH 2/3] migration: Drop unnecessary check in ram's pending_exact() peterx
2024-01-19 13:25 ` Fabiano Rosas
2024-03-20 17:51 ` Nina Schoetterl-Glausch
2024-03-20 18:05 ` Nina Schoetterl-Glausch
2024-03-20 18:57 ` Peter Xu
2024-03-20 19:21 ` Nina Schoetterl-Glausch
2024-03-20 19:46 ` Peter Xu
2024-03-20 20:45 ` Peter Xu
2024-01-17 7:58 ` [PATCH 3/3] analyze-migration.py: Remove trick on parsing ramblocks peterx
2024-01-19 13:23 ` Fabiano Rosas
2024-01-20 2:36 ` [PATCH 0/3] migration: some small cleanups Peter Xu
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=b91f763a-3d06-45aa-97af-3971e843514b@linaro.org \
--to=philmd@linaro.org \
--cc=bdas@redhat.com \
--cc=farosas@suse.de \
--cc=jusual@redhat.com \
--cc=peterx@redhat.com \
--cc=ppandit@redhat.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 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).