From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
acme@kernel.org, linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 4/4] tools lib traceevent: Implements '%' operation
Date: Tue, 23 Feb 2016 11:44:32 -0300 [thread overview]
Message-ID: <20160223144432.GB2749@redhat.com> (raw)
In-Reply-To: <20160223143819.GA2749@redhat.com>
Em Tue, Feb 23, 2016 at 11:38:19AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Mon, Feb 22, 2016 at 03:23:03PM -0500, Steven Rostedt escreveu:
> > On Mon, 22 Feb 2016 14:08:22 -0300
> > Daniel Bristot de Oliveira <bristot@redhat.com> wrote:
> >
> > > The operation '%' is not implemented on event-parse.c, causing
> > > an error on the parse of events with '%' operation on its
> > > printk format. For example,
> > >
> > > # perf record -e sched:sched_deadline_yield ~/y
> > > Warning: [sched:sched_deadline_yield] unknown op '%'
> > > ....
> > > # perf script
Daniel, please add two spaces before examples, specially examples with
the '#' root prompt.
Had I not done that when applying this patch, those lines would have
been removed by git-am, as it would interpret those as comments.
Thanks,
- Arnaldo
next prev parent reply other threads:[~2016-02-23 14:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 17:08 [PATCH 0/4] Tracepoints for deadline scheduler Daniel Bristot de Oliveira
2016-02-22 17:08 ` [PATCH 1/4] tracing: Add __print_ns_to_secs() and __print_ns_without_secs() helpers Daniel Bristot de Oliveira
2016-02-22 17:08 ` [PATCH 2/4] sched: Move deadline container_of() helper functions into sched.h Daniel Bristot de Oliveira
2016-02-22 17:08 ` [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Daniel Bristot de Oliveira
2016-02-22 17:32 ` Peter Zijlstra
2016-02-22 17:48 ` Steven Rostedt
2016-02-22 20:11 ` Daniel Bristot de Oliveira
2016-02-22 21:30 ` Peter Zijlstra
2016-02-22 22:30 ` Steven Rostedt
2016-02-23 10:40 ` Juri Lelli
2016-02-23 10:44 ` Peter Zijlstra
2016-02-23 13:10 ` Steven Rostedt
2016-02-24 8:48 ` Ingo Molnar
2016-02-23 14:27 ` Peter Zijlstra
2016-02-23 16:19 ` Daniel Bristot de Oliveira
2016-02-24 2:29 ` Daniel Bristot de Oliveira
2016-02-22 17:48 ` kbuild test robot
2016-02-22 17:08 ` [PATCH 4/4] tools lib traceevent: Implements '%' operation Daniel Bristot de Oliveira
2016-02-22 20:23 ` Steven Rostedt
2016-02-23 14:38 ` Arnaldo Carvalho de Melo
2016-02-23 14:44 ` Arnaldo Carvalho de Melo [this message]
2016-02-25 5:41 ` [tip:perf/core] tools lib traceevent: Implement " tip-bot for Daniel Bristot de Oliveira
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=20160223144432.GB2749@redhat.com \
--to=acme@redhat.com \
--cc=acme@kernel.org \
--cc=bristot@redhat.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).