From: Yordan Karadzhov <ykaradzhov@vmware.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org, y.karadz@gmail.com,
Yordan Karadzhov <ykaradzhov@vmware.com>
Subject: [PATCH 4/5] kernel-shark: Remove the definition of KS_DIR
Date: Tue, 23 Apr 2019 16:27:40 +0300 [thread overview]
Message-ID: <20190423132741.17864-5-ykaradzhov@vmware.com> (raw)
In-Reply-To: <20190423132741.17864-1-ykaradzhov@vmware.com>
KS_DIR is no longer used, so we do not need to define it in the
Cmake-generated header file.
Signed-off-by: Yordan Karadzhov <ykaradzhov@vmware.com>
---
kernel-shark/build/deff.h.cmake | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel-shark/build/deff.h.cmake b/kernel-shark/build/deff.h.cmake
index ba211f4..1cf8a80 100644
--- a/kernel-shark/build/deff.h.cmake
+++ b/kernel-shark/build/deff.h.cmake
@@ -11,9 +11,6 @@
/** KernelShark Version number. */
#cmakedefine KS_VERSION_STRING "@KS_VERSION_STRING@"
-/** KernelShark source code path. */
-#cmakedefine KS_DIR "@KS_DIR@"
-
/** KernelShark installation prefix path. */
#cmakedefine _INSTALL_PREFIX "@_INSTALL_PREFIX@"
--
2.20.1
next prev parent reply other threads:[~2019-04-23 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 13:27 [PATCH 0/5] Modifications needed for KS 1.0 Yordan Karadzhov
2019-04-23 13:27 ` [PATCH 1/5] kernel-shark: Add INSTALL PREFIX to the Cmake-generated header file Yordan Karadzhov
2019-04-23 13:27 ` [PATCH 2/5] kernel-shark: Add logic for the initial path of Open-File dialogs Yordan Karadzhov
2019-04-23 13:27 ` [PATCH 3/5] kernel-shark: Add logic for the plugins search path Yordan Karadzhov
2019-04-23 13:27 ` Yordan Karadzhov [this message]
2019-04-23 13:27 ` [PATCH 5/5] kernel-shark: Remember the paths used by the Open-File dialogs Yordan Karadzhov
2019-05-02 8:42 ` [PATCH 0/5] Modifications needed for KS 1.0 Slavomir Kaslev
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=20190423132741.17864-5-ykaradzhov@vmware.com \
--to=ykaradzhov@vmware.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).