All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: Steven Rostedt <rostedt@goodmis.org>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] trace-cmd fixes
Date: Wed, 24 Sep 2014 16:39:19 -0400	[thread overview]
Message-ID: <54232BF7.5090909@fb.com> (raw)

Hello,

I have a few outstanding trace-cmd patches that I've sent over the last 
couple of months, the bulk of which were while you were on vacation.  So 
here's a pull-able branch with the current backlog.  The 
"read_next_event" patch is authored today because I nuked the original 
git tree I had with it, but I sent it in July I think.  If these are 
acceptable you can just pull from

https://github.com/josefbacik/trace-cmd.git for-steve

Here is the shortlog

Josef Bacik (4):
       trace-cmd: make sure we have a pending pid in trace-hist
       trace-cmd: add trace-record.o to the python shared lib
       trace-cmd: add read_next_event to python lib
       trace-cmd: add helper to read kernel_stack functions

I've been carrying all but the kernel_stack thing internally for months 
and have scripts using them in production so they are well tested.  Thanks,

Josef

                 reply	other threads:[~2014-09-24 20:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=54232BF7.5090909@fb.com \
    --to=jbacik@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.