linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: sztsian@gmail.com
Cc: tz.stoyanov@gmail.com, linux-trace-devel@vger.kernel.org,
	Yordan Karadzhov <y.karadz@gmail.com>
Subject: Re: [PATCH 0/0] Two fixes for compiling
Date: Mon, 10 Feb 2020 11:39:27 -0500	[thread overview]
Message-ID: <20200210113927.49a4e0ca@gandalf.local.home> (raw)
In-Reply-To: <20200209034226.287464-1-sztsian@gmail.com>


Hi Zamir!

Thanks for the patches.

On Sun,  9 Feb 2020 11:42:24 +0800
sztsian@gmail.com wrote:

> This contains two fixes of compiling.
> 
> The KernelShark one is to inherit libdir into kernelshark CMakeLists so
> that the libdir parsed to Makefile is honored in kernelshark.

Yodan, can you review this one?

> 
> The trace-cmd one is to remove python-gui which depends on the obsoleted
> gtk stuff.
> 
> In order to compile and test this change, the following patch from
> Tzvetomir need to be applied.
> [PATCH] kernel-shark: Fix search path for libtracefs
> https://lore.kernel.org/linux-trace-devel/20200205070743.13836-1-tz.stoyanov@gmail.com/T/#u

I will start applying these.

> 
> Note: I always send email and git commits with signature "Zamir SUN"
> before. However I see DCO requires to sign using real name, so I changed
> to fulfill the DCO.
> 

Yes, thank you for doing so.

-- Steve

      parent reply	other threads:[~2020-02-10 16:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09  3:42 [PATCH 0/0] Two fixes for compiling sztsian
2020-02-09  3:42 ` [PATCH 1/2] KernelShark: Inherit libdir from Makefile sztsian
2020-02-17 11:26   ` Yordan Karadzhov (VMware)
2020-02-17 13:24     ` Zamir SUN
2020-02-17 14:11       ` Yordan Karadzhov (VMware)
2020-02-21 10:46         ` Yordan Karadzhov (VMware)
2020-02-21 11:56           ` Zamir SUN
2020-02-09  3:42 ` [PATCH 2/2] trace-cmd: Clean up old gtk stuff sztsian
2020-02-10 16:39 ` 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=20200210113927.49a4e0ca@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=sztsian@gmail.com \
    --cc=tz.stoyanov@gmail.com \
    --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).