From: Slavomir Kaslev <kaslevs@vmware.com>
To: Yordan Karadzhov <ykaradzhov@vmware.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>,
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: Re: [PATCH 0/6] Various modifications and fixes toward KS 1.0
Date: Thu, 16 May 2019 13:42:41 +0000 [thread overview]
Message-ID: <CAE0o1NuLW1E7wayZA2CKtDGp4YciJjVz9-4KFkk+XWiB+GyDLA@mail.gmail.com> (raw)
In-Reply-To: <20190515190911.20755-1-ykaradzhov@vmware.com>
On Wed, May 15, 2019 at 10:11 PM Yordan Karadzhov <ykaradzhov@vmware.com> wrote:
>
> The patch-set contains patches that have been sent already,
> but have not been pushed due to various reasons. The last
> two patch are fixes of bugs that have been found recently.
>
>
> Yordan Karadzhov (6):
> kernel-shark: Remove hard-coded install paths
> kernel-shark: Use XDG compliant path when saving cached data
> kernel-shark: Enforce update of the OpenGL widget when loading new
> session
> kernel-shark: Add "Report bug" button to "Help"
> kernel-shark: Improve the appearance on high screen resolution
> kernel-shark: Handle the case when the marker points to a filtered
> entry
>
> kernel-shark/CMakeLists.txt | 8 ++++--
> kernel-shark/build/deff.h.cmake | 3 ++
> kernel-shark/build/ks.desktop.cmake | 4 +--
> kernel-shark/src/CMakeLists.txt | 19 +++++++------
> kernel-shark/src/KsDualMarker.cpp | 9 ++++++
> kernel-shark/src/KsGLWidget.cpp | 24 +++++++++-------
> kernel-shark/src/KsGLWidget.hpp | 5 +++-
> kernel-shark/src/KsMainWindow.cpp | 22 ++++++++++++---
> kernel-shark/src/KsMainWindow.hpp | 4 +++
> kernel-shark/src/KsPlotTools.cpp | 37 +++++++++++++++++++++++--
> kernel-shark/src/KsPlotTools.hpp | 11 +++++++-
> kernel-shark/src/KsTraceGraph.cpp | 2 ++
> kernel-shark/src/KsTraceViewer.cpp | 22 +++++++++------
> kernel-shark/src/KsUtils.cpp | 4 +--
> kernel-shark/src/plugins/CMakeLists.txt | 3 +-
> 15 files changed, 134 insertions(+), 43 deletions(-)
All the new patches looks good to me.
Reviewed-by: Slavomir Kaslev <kaslevs@vmware.com>
Thanks!
-- Slavi
next prev parent reply other threads:[~2019-05-16 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 19:09 [PATCH 0/6] Various modifications and fixes toward KS 1.0 Yordan Karadzhov
2019-05-15 19:09 ` [PATCH 1/6] kernel-shark: Remove hard-coded install paths Yordan Karadzhov
2019-05-15 19:09 ` [PATCH 2/6] kernel-shark: Use XDG compliant path when saving cached data Yordan Karadzhov
2019-05-15 19:09 ` [PATCH 3/6] kernel-shark: Enforce update of the OpenGL widget when loading new session Yordan Karadzhov
2019-05-15 19:09 ` [PATCH 4/6] kernel-shark: Add "Report bug" button to "Help" Yordan Karadzhov
2019-05-15 19:09 ` [PATCH 5/6] kernel-shark: Improve the appearance on high screen resolution Yordan Karadzhov
2019-05-15 19:09 ` [PATCH 6/6] kernel-shark: Handle the case when the marker points to a filtered entry Yordan Karadzhov
2019-05-16 13:42 ` Slavomir Kaslev [this message]
2019-05-21 13:59 ` [PATCH 0/6] Various modifications and fixes toward KS 1.0 Steven Rostedt
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=CAE0o1NuLW1E7wayZA2CKtDGp4YciJjVz9-4KFkk+XWiB+GyDLA@mail.gmail.com \
--to=kaslevs@vmware.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=slavomir.kaslev@gmail.com \
--cc=y.karadz@gmail.com \
--cc=ykaradzhov@vmware.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).