From: Thomas Huth <thuth@redhat.com>
To: Mao Zhongyi <maozhongyi@cmss.chinamobile.com>, qemu-devel@nongnu.org
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
tony.nguyen@bt.com, alex.bennee@linaro.org, armbru@redhat.com,
laurent@vivier.eu
Subject: Re: [PATCH v3 2/3] tests/migration: fix a typo in comment
Date: Mon, 7 Oct 2019 17:09:29 +0200 [thread overview]
Message-ID: <d3984a36-0aea-7a3f-dd87-1cbf721d0a41@redhat.com> (raw)
In-Reply-To: <927b1b1f9365e0d5d9683746b498c16b88405174.1570159624.git.maozhongyi@cmss.chinamobile.com>
On 04/10/2019 05.43, Mao Zhongyi wrote:
> Signed-off-by: Mao Zhongyi <maozhongyi@cmss.chinamobile.com>
> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> Reviewed-by: Laurent Vivier <laurent@vivier.eu>
> ---
> tests/migration/stress.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/migration/stress.c b/tests/migration/stress.c
> index 9e128eef50..debf34359f 100644
> --- a/tests/migration/stress.c
> +++ b/tests/migration/stress.c
> @@ -191,7 +191,7 @@ static int stressone(unsigned long long ramsizeMB)
>
> /* We don't care about initial state, but we do want
> * to fault it all into RAM, otherwise the first iter
> - * of the loop below will be quite slow. We cna't use
> + * of the loop below will be quite slow. We can't use
> * 0x0 as the byte as gcc optimizes that away into a
> * calloc instead :-) */
> memset(ram, 0xfe, ramsizeMB * 1024 * 1024);
>
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2019-10-07 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 3:43 [PATCH v3 0/3] some fix in tests/migration Mao Zhongyi
2019-10-04 3:43 ` [PATCH v3 1/3] tests/migration: mem leak fix Mao Zhongyi
2019-10-04 7:17 ` Laurent Vivier
2019-10-04 3:43 ` [PATCH v3 2/3] tests/migration: fix a typo in comment Mao Zhongyi
2019-10-07 15:09 ` Thomas Huth [this message]
2019-10-04 3:43 ` [PATCH v3 3/3] tests/migration:fix unreachable path in stress test Mao Zhongyi
2019-10-04 7:20 ` Laurent Vivier
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=d3984a36-0aea-7a3f-dd87-1cbf721d0a41@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=laurent@vivier.eu \
--cc=maozhongyi@cmss.chinamobile.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=tony.nguyen@bt.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).