All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v2] trace-cmd: Re-enable the build of KernelShark v1
Date: Wed, 16 Dec 2020 18:00:33 -0500	[thread overview]
Message-ID: <20201216180033.7592f75a@gandalf.local.home> (raw)
In-Reply-To: <20201216171944.230cc08a@gandalf.local.home>

On Wed, 16 Dec 2020 17:19:44 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:

> Ideally, we don't want to include the libtraceevent or libtracefs system
> includes when building locally. Let me see if I can fix the make file here.

Can you apply this? It should fix the build problem with libtraceevent,
without having to touch any of its files.

  https://patchwork.kernel.org/project/linux-trace-devel/patch/20201216175138.2d1a9b34@gandalf.local.home/

-- Steve


      reply	other threads:[~2020-12-16 23:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 13:07 [PATCH v2] trace-cmd: Re-enable the build of KernelShark v1 Yordan Karadzhov (VMware)
2020-12-16 20:26 ` Steven Rostedt
2020-12-16 20:28 ` Steven Rostedt
2020-12-16 22:19   ` Steven Rostedt
2020-12-16 23:00     ` 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=20201216180033.7592f75a@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.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 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.