From: Steven Rostedt <rostedt@goodmis.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
"zhangwei(Jovi)" <jovi.zhangwei@huawei.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] tracing: more list_empty(perf_events) checks
Date: Thu, 18 Jul 2013 11:53:26 -0400 [thread overview]
Message-ID: <1374162806.6458.238.camel@gandalf.local.home> (raw)
In-Reply-To: <20130718154403.GA8416@redhat.com>
On Thu, 2013-07-18 at 17:44 +0200, Oleg Nesterov wrote:
> Steven, I am starting to think that it would be better to resend this
> series (3-6 in mbox I sent) so that Peter and Frederic can take another
> look. And I'll try to update the changelogs. Will do a bit later today.
Or do you mean 4-6? As I applied 1-3 already, and added Peter's
Acked-by.
I'm guessing 1-3's change logs were good enough.
-- Steve
next prev parent reply other threads:[~2013-07-18 15:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 17:01 [PATCH 0/3] tracing: more list_empty(perf_events) checks Oleg Nesterov
2013-06-17 17:02 ` [PATCH 1/3] tracing/function: Avoid perf_trace_buf_*() if event_function.perf_events is empty Oleg Nesterov
2013-06-17 17:02 ` [PATCH 2/3] tracing/syscall: Avoid perf_trace_buf_*() if sys_data->perf_events " Oleg Nesterov
2013-06-17 17:02 ` [PATCH 3/3] tracing/perf: Move the PERF_MAX_TRACE_SIZE check into perf_trace_buf_prepare() Oleg Nesterov
2013-06-17 20:18 ` [PATCH 0/3] tracing: more list_empty(perf_events) checks Oleg Nesterov
2013-06-17 21:27 ` Steven Rostedt
2013-06-18 14:46 ` Oleg Nesterov
2013-06-18 15:41 ` Steven Rostedt
2013-06-18 16:24 ` Oleg Nesterov
2013-07-18 3:00 ` Steven Rostedt
2013-07-18 9:42 ` Peter Zijlstra
2013-07-18 14:39 ` Steven Rostedt
2013-07-18 15:44 ` Oleg Nesterov
2013-07-18 15:53 ` Steven Rostedt [this message]
2013-07-18 16:11 ` Oleg Nesterov
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=1374162806.6458.238.camel@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=jovi.zhangwei@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.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 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.