linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Cc: "linux-trace-devel@vger.kernel.org" <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH 0/3] libtraceevent: Various API fixes
Date: Mon, 26 Nov 2018 09:34:04 -0500	[thread overview]
Message-ID: <20181126093404.446ca4d3@gandalf.local.home> (raw)
In-Reply-To: <20181123133946.16239-1-tstoyanov@vmware.com>

On Fri, 23 Nov 2018 13:39:58 +0000
Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:

> This patch series contains few unrelated changes in 
> the library APIs. It improves the consistency of the APIs
> return logic and removes a duplicated API. 
> 
> Tzvetomir Stoyanov (3):
>   tools/lib/traceevent: Remove tep_data_event_from_type() API
>   tools/lib/traceevent: Changed return logic of
>     tep_register_event_handler() API
>   tools/lib/traceevent: Changed return logic of trace_seq_printf() and
>     trace_seq_vprintf() APIs
> 
>  .../libtraceevent-reg_event_handler.txt       | 12 +++++++---
>  .../libtraceevent-tseq_print.txt              |  9 ++++----
>  .../Documentation/libtraceevent.txt           |  1 -
>  tools/lib/traceevent/event-parse.c            | 22 +++++++------------
>  tools/lib/traceevent/event-parse.h            |  6 ++++-
>  tools/lib/traceevent/trace-seq.c              | 17 +++++++++-----
>  6 files changed, 39 insertions(+), 28 deletions(-)
> 

This doesn't appear to apply on any tree.

Note, if you send a patch series, it must apply on the tree you are
sending it to. It should not depend on any patch that is pending and
has not yet been applied. If it does, then that pending patch needs to
be added to the series as well.

-- Steve

      parent reply	other threads:[~2018-11-27  1:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 13:39 [PATCH 0/3] libtraceevent: Various API fixes Tzvetomir Stoyanov
2018-11-23 13:40 ` [PATCH 1/3] tools/lib/traceevent: Remove tep_data_event_from_type() API Tzvetomir Stoyanov
2018-11-23 13:40 ` [PATCH 2/3] tools/lib/traceevent: Changed return logic of tep_register_event_handler() API Tzvetomir Stoyanov
2018-11-23 13:40 ` [PATCH 3/3] tools/lib/traceevent: Changed return logic of trace_seq_printf() and trace_seq_vprintf() APIs Tzvetomir Stoyanov
2018-11-26 14:34 ` Steven Rostedt [this message]

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=20181126093404.446ca4d3@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=tstoyanov@vmware.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 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).