linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
	John 'Warthog9' Hawley <warthog9@kernel.org>
Subject: Re: [PATCH] libtracefs: Remove "traceevent/" from referencing libtraceevent headers
Date: Mon, 26 Jul 2021 11:24:42 -0400	[thread overview]
Message-ID: <20210726112442.4574ffba@oasis.local.home> (raw)
In-Reply-To: <a359be7c-3d90-7941-2eee-d8cdc225e4a5@gmail.com>

On Mon, 26 Jul 2021 13:25:41 +0300
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:

> > diff --git a/include/tracefs.h b/include/tracefs.h
> > index 7e1927b..2649417 100644
> > --- a/include/tracefs.h
> > +++ b/include/tracefs.h
> > @@ -9,7 +9,7 @@
> >   #include <sys/stat.h>
> >   #include <fcntl.h>
> >   #include <sched.h>
> > -#include <traceevent/event-parse.h>
> > +#include <event-parse.h>  
> 
> Perhaps we need a similar patch for "trace-cmd.h".

Like this?

  https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/commit/?h=trace-cmd-stable-v2.9&id=c3bf2ced24528debba6e6c48c77e3868cdb3dec1


I pushed it for v2.9 because it was broken if libtraceeevent was
installed. I'll make sure it's there for the development branch as well.

-- Steve

      reply	other threads:[~2021-07-26 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-17  2:06 [PATCH] libtracefs: Remove "traceevent/" from referencing libtraceevent headers Steven Rostedt
2021-07-17  3:00 ` Steven Rostedt
2021-07-26 10:25 ` Yordan Karadzhov (VMware)
2021-07-26 15:24   ` 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=20210726112442.4574ffba@oasis.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=warthog9@kernel.org \
    --cc=y.karadz@gmail.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).