Re: [RFC 1/7] kernel-shark: kshark_string_config_alloc() must take no arguments

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [RFC 1/7] kernel-shark: kshark_string_config_alloc() must take no arguments
From: Steven Rostedt <rostedt@xxxxxxxxxxx>
Date: Wed, 27 Mar 2019 12:19:01 -0400
Cc: linux-trace-devel@xxxxxxxxxxxxxxx, y.karadz@xxxxxxxxx
In-reply-to: <20190327160323.31654-2-ykaradzhov@vmware.com>
References: <20190327160323.31654-1-ykaradzhov@vmware.com> <20190327160323.31654-2-ykaradzhov@vmware.com>

On Wed, 27 Mar 2019 18:03:17 +0200
Yordan Karadzhov <ykaradzhov@xxxxxxxxxx> 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

References:
- [RFC 0/7] NumPy Interface for KernelShark
  - From: Yordan Karadzhov
- [RFC 1/7] kernel-shark: kshark_string_config_alloc() must take no arguments
  - From: Yordan Karadzhov

Prev by Date: [RFC 7/7] kernel-shark: Add basic example demonstrating the NumPy interface
Next by Date: Re: [RFC 4/7] kernel-shark: Add the core components of the NumPy API
Previous by thread: [RFC 1/7] kernel-shark: kshark_string_config_alloc() must take no arguments
Next by thread: [RFC 2/7] kernel-shark: Add new dataloading method to be used by the NumPu interface
Index(es):
- Date
- Thread

[Index of Archives] [Linux USB Development] [Linux USB Development] [Linux Audio Users] [Yosemite Hiking] [Linux Kernel] [Linux SCSI]

Powered by Linux