From: Alon Levy <alevy@redhat.com>
To: "Stefan Hajnoczi" <stefanha@gmail.com>,
"Lluís Vilanova" <vilanova@ac.upc.edu>,
qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH trivial] trace-events: don't use dtrace reserved words in and next
Date: Wed, 28 Mar 2012 15:33:45 +0200 [thread overview]
Message-ID: <20120328133345.GZ32389@garlic> (raw)
In-Reply-To: <20120328131634.GY32389@garlic>
On Wed, Mar 28, 2012 at 03:16:34PM +0200, Alon Levy wrote:
> On Wed, Mar 28, 2012 at 01:55:49PM +0100, Stefan Hajnoczi wrote:
> > On Wed, Mar 28, 2012 at 8:55 AM, Alon Levy <alevy@redhat.com> wrote:
> > > ---
> > > trace-events | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > We're always going to struggle with new trace events that add reserved
> > keywords. Fixing up trace-events is going to be an ongoing task so
> > I'd like to also see tracetool automatically modify keywords 'next' ->
> > 'next_'. Do you want to send a patch to do that instead?
>
hmm, I changed to _next, not next_, if you'd like to change that and
commit I don't mind.
> sure. For the new tracetool.py too ? :)
>
> >
> > Stefan
> >
>
next prev parent reply other threads:[~2012-03-28 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 7:55 [Qemu-devel] [PATCH trivial] trace-events: don't use dtrace reserved words in and next Alon Levy
2012-03-28 12:55 ` Stefan Hajnoczi
2012-03-28 13:16 ` Alon Levy
2012-03-28 13:32 ` [Qemu-trivial] [PATCH 1/2] tracetool: dtrace: handle in and next reserved words Alon Levy
2012-03-28 13:32 ` [Qemu-trivial] [PATCH 2/2] tracetool: dtrace: warn on reserved word usage Alon Levy
2012-03-28 13:33 ` Alon Levy [this message]
2012-03-28 13:35 ` [Qemu-devel] [PATCH trivial] trace-events: don't use dtrace reserved words in and next Stefan Hajnoczi
2012-03-28 14:26 ` [Qemu-devel] [PATCH 1/2] tracetool: dtrace: handle in and next reserved words Alon Levy
2012-03-28 14:26 ` [Qemu-devel] [PATCH 2/2] tracetool: dtrace: warn on reserved word usage Alon Levy
2012-03-28 16:26 ` [Qemu-devel] [PATCH 1/2] tracetool: dtrace: handle in and next reserved words Lee Essen
2012-03-28 16:38 ` Eric Blake
2012-03-28 16:43 ` Peter Maydell
2012-03-29 21:35 ` [Qemu-trivial] [PATCH v3 " Alon Levy
2012-03-29 21:35 ` [Qemu-trivial] [PATCH 2/2] tracetool: dtrace: warn on reserved word usage Alon Levy
2012-03-30 11:00 ` Stefan Hajnoczi
2012-03-30 10:58 ` [Qemu-trivial] [PATCH v3 1/2] tracetool: dtrace: handle in and next reserved words Stefan Hajnoczi
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=20120328133345.GZ32389@garlic \
--to=alevy@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.