qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: jemmy858585@gmail.com
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com, qemu-block@nongnu.org,
	Lidong Chen <lidongchen@tencent.com>
Subject: [Qemu-devel] [PATCH 2/2] qemu-img: fix some spelling errors
Date: Sun, 23 Apr 2017 22:33:17 +0800	[thread overview]
Message-ID: <1492957997-28587-2-git-send-email-lidongchen@tencent.com> (raw)
In-Reply-To: <1492957997-28587-1-git-send-email-lidongchen@tencent.com>

From: Lidong Chen <lidongchen@tencent.com>

Fix some spelling errors in is_allocated_sectors comment.

Signed-off-by: Lidong Chen <lidongchen@tencent.com>
---
 qemu-img.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/qemu-img.c b/qemu-img.c
index df6d165..0b3349c 100644
--- a/qemu-img.c
+++ b/qemu-img.c
@@ -1033,8 +1033,8 @@ done:
 }
 
 /*
- * Returns true iff the first sector pointed to by 'buf' contains at least
- * a non-NUL byte.
+ * Returns true if the first sector pointed to by 'buf' contains at least
+ * a non-NULL byte.
  *
  * 'pnum' is set to the number of sectors (including and immediately following
  * the first one) that are known to be in the same allocated/unallocated state.
-- 
1.8.3.1

  reply	other threads:[~2017-04-23 14:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-23 14:33 [Qemu-devel] [PATCH 1/2] qemu-img: make sure contain the consecutive number of zero bytes jemmy858585
2017-04-23 14:33 ` jemmy858585 [this message]
2017-04-24 14:40   ` [Qemu-devel] [PATCH 2/2] qemu-img: fix some spelling errors Eric Blake
2017-04-24 15:37     ` Philippe Mathieu-Daudé
2017-04-24 15:47       ` Eric Blake
2017-04-24 15:53         ` Eric Blake
2017-04-25  2:10           ` 858585 jemmy
2017-04-25 19:11           ` Max Reitz
2017-04-26  8:05             ` 858585 jemmy
2017-04-24 14:43 ` [Qemu-devel] [PATCH 1/2] qemu-img: make sure contain the consecutive number of zero bytes Eric Blake
2017-04-25  1:50   ` 858585 jemmy
2017-04-25 19:20     ` Eric Blake
2017-04-25 20:01     ` Max Reitz

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=1492957997-28587-2-git-send-email-lidongchen@tencent.com \
    --to=jemmy858585@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=lidongchen@tencent.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).