linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yordan Karadzhov <y.karadz@gmail.com>
To: linux-trace-devel@vger.kernel.org
Cc: hongzhan.chen@intel.com, jan.kiszka@siemens.com
Subject: Re: [PATCH 0/2] kernel-shark: Fixes needed by the Xenomai plugin
Date: Mon, 21 Feb 2022 14:31:55 +0200	[thread overview]
Message-ID: <f12f509c-0ff2-8f83-869f-b91aa7076baf@gmail.com> (raw)
In-Reply-To: <20220216082909.614231-1-y.karadz@gmail.com>

Hi Hongzan and Jan,

The modifications needed by the plugin are now upstream and I would like to ask you to do one last thing. When you are 
ready with the plugin and its stand-alone repo, please send me a patch, adding to the README file of kernelshark a short 
description of your plugin (couple of sentences) and a link for its repo. This way others can take ideas and inspiration 
from what you did.

thanks!
Yordan

On 16.02.22 г. 10:29 ч., Yordan Karadzhov (VMware) wrote:
> Yordan Karadzhov (VMware) (2):
>    kernel-shark: Add KsPluginsGUI.hpp/.cpp
>    kernel-shark: Load 'ctrl' interface for user plugins
> 
>   src/CMakeLists.txt   |  5 +++++
>   src/KsPluginsGUI.cpp | 27 +++++++++++++++++++++++++++
>   src/KsPluginsGUI.hpp | 22 ++++++++++++++++++++++
>   src/KsUtils.cpp      | 35 +++++++++++++++++++++++++----------
>   src/KsUtils.hpp      |  2 ++
>   5 files changed, 81 insertions(+), 10 deletions(-)
>   create mode 100644 src/KsPluginsGUI.cpp
>   create mode 100644 src/KsPluginsGUI.hpp
> 

      parent reply	other threads:[~2022-02-21 12:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16  8:29 [PATCH 0/2] kernel-shark: Fixes needed by the Xenomai plugin Yordan Karadzhov (VMware)
2022-02-16  8:29 ` [PATCH 1/2] kernel-shark: Add KsPluginsGUI.hpp/.cpp Yordan Karadzhov (VMware)
2022-02-16  8:29 ` [PATCH 2/2] kernel-shark: Load 'ctrl' interface for user plugins Yordan Karadzhov (VMware)
2022-02-21 12:31 ` Yordan Karadzhov [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=f12f509c-0ff2-8f83-869f-b91aa7076baf@gmail.com \
    --to=y.karadz@gmail.com \
    --cc=hongzhan.chen@intel.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-trace-devel@vger.kernel.org \
    /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).