From: Oleg Nesterov <oleg@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] tracing: minor cleanups
Date: Thu, 18 Jul 2013 20:46:47 +0200 [thread overview]
Message-ID: <20130718184647.GA4761@redhat.com> (raw)
Steven,
As you suggested, I extracted 2/2 into the separate change.
I think that it and 1/2 makes sense in any case so I am sending
them right now. This shrinks the next series I am trying to make.
Oleg.
next reply other threads:[~2013-07-18 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 18:46 Oleg Nesterov [this message]
2013-07-18 18:47 ` [PATCH 1/2] tracing: Simplify the iteration logic in f_start/f_next Oleg Nesterov
2013-07-18 18:47 ` [PATCH 2/2] tracing: Do not (ab)use trace_seq in event_id_read() 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=20130718184647.GA4761@redhat.com \
--to=oleg@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=rostedt@goodmis.org \
/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