From: Steven Rostedt <rostedt@goodmis.org>
To: Yordan Karadzhov <ykaradzhov@vmware.com>
Cc: linux-trace-devel@vger.kernel.org, y.karadz@gmail.com
Subject: Re: [RFC 1/7] kernel-shark: kshark_string_config_alloc() must take no arguments
Date: Wed, 27 Mar 2019 12:19:01 -0400 [thread overview]
Message-ID: <20190327121901.6e24f550@gandalf.local.home> (raw)
In-Reply-To: <20190327160323.31654-2-ykaradzhov@vmware.com>
On Wed, 27 Mar 2019 18:03:17 +0200
Yordan Karadzhov <ykaradzhov@vmware.com> wrote:
> The function is not meant to have arguments, so it must explicitly
> state this. A functions taking unspecified list of parameters will
> be a problem for the Pythion interface.
I applied this now, because it is a real fix.
-- Steve
next prev parent reply other threads:[~2019-03-27 16:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 16:03 [RFC 0/7] NumPy Interface for KernelShark Yordan Karadzhov
2019-03-27 16:03 ` [RFC 1/7] kernel-shark: kshark_string_config_alloc() must take no arguments Yordan Karadzhov
2019-03-27 16:19 ` Steven Rostedt [this message]
2019-03-27 16:03 ` [RFC 2/7] kernel-shark: Add new dataloading method to be used by the NumPu interface Yordan Karadzhov
2019-03-27 23:41 ` Slavomir Kaslev
2019-03-27 16:03 ` [RFC 3/7] kernel-shark: Prepare for building the NumPy interface Yordan Karadzhov
2019-03-27 16:03 ` [RFC 4/7] kernel-shark: Add the core components of the NumPy API Yordan Karadzhov
2019-03-27 22:53 ` Slavomir Kaslev
2019-03-27 16:03 ` [RFC 5/7] kernel-shark: Add Numpy Interface for processing of tracing data Yordan Karadzhov
2019-03-27 16:03 ` [RFC 6/7] kernel-shark: Add automatic building of the NumPy interface Yordan Karadzhov
2019-03-27 16:03 ` [RFC 7/7] kernel-shark: Add basic example demonstrating " Yordan Karadzhov
2019-03-27 23:25 ` Slavomir Kaslev
2019-03-28 12:47 ` Slavomir Kaslev
2019-04-05 10:10 ` 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=20190327121901.6e24f550@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--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).