From: Stefan Hajnoczi <stefanha@redhat.com>
To: Qinghua Jin <qhjin_dev@163.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-trivial][PATCH] trace: reflect the file name change
Date: Mon, 14 Dec 2015 20:21:34 +0800 [thread overview]
Message-ID: <20151214122134.GF5027@stefanha-x1.localdomain> (raw)
In-Reply-To: <6aa1b449.fb8b.1518fdc8641.Coremail.qhjin_dev@163.com>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
On Fri, Dec 11, 2015 at 03:06:12PM +0800, Qinghua Jin wrote:
> Some functions was moved from block.c to block/io.c, so the trace-events file should reflect that change.
>
>
> Signed-off-by: Qinghua Jin <qhjin_dev@163.com>
> ---
> trace-events | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Please use git-send-email(1) in the future. I had to manually apply
your patch.
Thanks, applied to my tracing-next tree:
https://github.com/stefanha/qemu/commits/tracing-next
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-15 3:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 7:06 [Qemu-devel] [Qemu-trivial][PATCH] trace: reflect the file name change Qinghua Jin
2015-12-14 12:21 ` Stefan Hajnoczi [this message]
2015-12-15 14:12 ` Qinghua Jin
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=20151214122134.GF5027@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=qhjin_dev@163.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).