From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Lluís Vilanova" <vilanova@ac.upc.edu>,
"Anthony Liguori" <aliguori@amazon.com>
Subject: [Qemu-devel] [PULL 6/6] trace-events: Fix typo in "offset"
Date: Wed, 19 Feb 2014 16:45:59 +0100 [thread overview]
Message-ID: <1392824759-7093-7-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1392824759-7093-1-git-send-email-stefanha@redhat.com>
From: Kevin Wolf <kwolf@redhat.com>
s/offet/offset/
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
trace-events | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/trace-events b/trace-events
index ab11f97..3713063 100644
--- a/trace-events
+++ b/trace-events
@@ -495,10 +495,10 @@ qcow2_writev_done_part(void *co, int cur_nr_sectors) "co %p cur_nr_sectors %d"
qcow2_writev_data(void *co, uint64_t offset) "co %p offset %" PRIx64
# block/qcow2-cluster.c
-qcow2_alloc_clusters_offset(void *co, uint64_t offset, int num) "co %p offet %" PRIx64 " num %d"
-qcow2_handle_copied(void *co, uint64_t guest_offset, uint64_t host_offset, uint64_t bytes) "co %p guest_offet %" PRIx64 " host_offset %" PRIx64 " bytes %" PRIx64
-qcow2_handle_alloc(void *co, uint64_t guest_offset, uint64_t host_offset, uint64_t bytes) "co %p guest_offet %" PRIx64 " host_offset %" PRIx64 " bytes %" PRIx64
-qcow2_do_alloc_clusters_offset(void *co, uint64_t guest_offset, uint64_t host_offset, int nb_clusters) "co %p guest_offet %" PRIx64 " host_offset %" PRIx64 " nb_clusters %d"
+qcow2_alloc_clusters_offset(void *co, uint64_t offset, int num) "co %p offset %" PRIx64 " num %d"
+qcow2_handle_copied(void *co, uint64_t guest_offset, uint64_t host_offset, uint64_t bytes) "co %p guest_offset %" PRIx64 " host_offset %" PRIx64 " bytes %" PRIx64
+qcow2_handle_alloc(void *co, uint64_t guest_offset, uint64_t host_offset, uint64_t bytes) "co %p guest_offset %" PRIx64 " host_offset %" PRIx64 " bytes %" PRIx64
+qcow2_do_alloc_clusters_offset(void *co, uint64_t guest_offset, uint64_t host_offset, int nb_clusters) "co %p guest_offset %" PRIx64 " host_offset %" PRIx64 " nb_clusters %d"
qcow2_cluster_alloc_phys(void *co) "co %p"
qcow2_cluster_link_l2(void *co, int nb_clusters) "co %p nb_clusters %d"
--
1.8.5.3
next prev parent reply other threads:[~2014-02-19 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 15:45 [Qemu-devel] [PULL 0/6] Tracing patches Stefan Hajnoczi
2014-02-19 15:45 ` [Qemu-devel] [PULL 1/6] Fix configure script for LTTng 2.x Stefan Hajnoczi
2014-02-19 15:45 ` [Qemu-devel] [PULL 2/6] Modified the tracetool framework " Stefan Hajnoczi
2014-02-19 15:45 ` [Qemu-devel] [PULL 3/6] Adapt Makefiles to the new LTTng ust interface Stefan Hajnoczi
2014-02-19 15:45 ` [Qemu-devel] [PULL 4/6] Update documentation for LTTng ust tracing Stefan Hajnoczi
2014-02-19 15:45 ` [Qemu-devel] [PULL 5/6] Add ust generated files to .gitignore Stefan Hajnoczi
2014-02-19 15:45 ` Stefan Hajnoczi [this message]
2014-02-19 16:01 ` [Qemu-devel] [PULL 0/6] Tracing patches Lluís Vilanova
2014-02-20 10:24 ` Stefan Hajnoczi
2014-02-21 14:46 ` Peter Maydell
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=1392824759-7093-7-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=aliguori@amazon.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vilanova@ac.upc.edu \
/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).