From: Stefan Hajnoczi <stefanha@redhat.com>
To: Yaowei Bai <baiyaowei@cmss.chinamobile.com>
Cc: famz@redhat.com, kwolf@redhat.com, mreitz@redhat.com,
pbonzini@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] timer: fix misleading comment in timer.h
Date: Thu, 1 Dec 2016 13:50:08 +0000 [thread overview]
Message-ID: <20161201135008.GK10441@stefanha-x1.localdomain> (raw)
In-Reply-To: <1480566640-27264-1-git-send-email-baiyaowei@cmss.chinamobile.com>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
On Wed, Nov 30, 2016 at 11:30:38PM -0500, Yaowei Bai wrote:
> It's timer to expire, not clock.
>
> Signed-off-by: Yaowei Bai <baiyaowei@cmss.chinamobile.com>
> ---
> include/qemu/timer.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
For the whole series:
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
PS: I suggest sending a cover letter "[PATCH 0/3]" in the future. This
makes it easy for reviewers to indicate they have reviewed the whole
series. Without a cover letter it's ambiguous whether my single
Reviewed-by: applies to just this patch or to the whole series - and
patch management tools will probably get it wrong too.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-12-01 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 4:30 [Qemu-devel] [PATCH 1/3] timer: fix misleading comment in timer.h Yaowei Bai
2016-12-01 4:30 ` [Qemu-devel] [PATCH 2/3] main-loop: update comment for qemu_mutex_lock/unlock_iothread Yaowei Bai
2016-12-01 4:30 ` [Qemu-devel] [PATCH 3/3] block: drop remaining legacy aio functions in comment Yaowei Bai
2016-12-01 13:50 ` Stefan Hajnoczi [this message]
2016-12-01 15:23 ` [Qemu-devel] [PATCH 1/3] timer: fix misleading comment in timer.h Paolo Bonzini
2016-12-05 3:08 ` Yaowei Bai
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=20161201135008.GK10441@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@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).