From: Michal Sojka <michal.sojka@cvut.cz>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-trace-devel@vger.kernel.org,
Michal Sojka <michal.sojka@cvut.cz>
Subject: [PATCH 0/4] kernel-shark: CMake changes
Date: Wed, 17 Mar 2021 17:40:57 +0100 [thread overview]
Message-ID: <20210317164101.30848-1-michal.sojka@cvut.cz> (raw)
This patch series is a follow up to my previous patch for the older
kernel-shark repo. The first two patches will make life easier for
distributions like NixOS, the last two patches replace my previous
patch.
Note that I didn't add kshark-su-record to a separate component, as
suggested by Yordan, because it is not necessary. The generated polkit
action will refer to the correct path and I think it is preferable to
have all kernelshark binaries in the same directory.
Michal Sojka (4):
kernel-shark: Allow specifying PKG_CONFIG_DIR on cmake command line
kernel-shark: Allow specifying TT_FONT_FILE on cmake command line
kernel-shark: Allow installing polkit policy separately
kernel-shark: Do not use sudo in install_gui.sh + update README
CMakeLists.txt | 12 ++++++++++--
README | 2 +-
build/install_gui.sh | 10 +++++++++-
src/CMakeLists.txt | 10 ++++++----
4 files changed, 26 insertions(+), 8 deletions(-)
--
2.30.1
next reply other threads:[~2021-03-17 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 16:40 Michal Sojka [this message]
2021-03-17 16:40 ` [PATCH 1/4] kernel-shark: Allow specifying PKG_CONFIG_DIR on cmake command line Michal Sojka
2021-03-17 16:40 ` [PATCH 2/4] kernel-shark: Allow specifying TT_FONT_FILE " Michal Sojka
2021-03-17 16:41 ` [PATCH 3/4] kernel-shark: Allow installing polkit policy separately Michal Sojka
2021-03-17 16:41 ` [PATCH 4/4] kernel-shark: Do not use sudo in install_gui.sh + update README Michal Sojka
2021-03-23 13:45 ` [PATCH 0/4] kernel-shark: CMake changes Yordan Karadzhov (VMware)
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=20210317164101.30848-1-michal.sojka@cvut.cz \
--to=michal.sojka@cvut.cz \
--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).