chars in trace-event-native.
Is it better to introduce a line break than to have a 83-chars
long line?
- in trace-event-scripting.c a struct is declared as extern. Here,
I followed what was already done for perl/python scripting.
Signed-off-by: Adrien BAK
---
diff --g
Commit-ID: ffa91880a992ec1aaee4b4f7c9ddffda0c277ba9
Gitweb: http://git.kernel.org/tip/ffa91880a992ec1aaee4b4f7c9ddffda0c277ba9
Author: Adrien BAK
AuthorDate: Fri, 18 Apr 2014 11:00:43 +0900
Committer: Jiri Olsa
CommitDate: Sun, 20 Apr 2014 00:15:12 +0200
perf tools: Improve error
orting in
tools/perf/util/data.c open_file_write
Currently, if the call to open fails, the user is unaware of it.
This patch logs the error, before returning the error code to the caller.
Signed-off-by: Adrien BAK
---
diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
index eb5
able (error) in trace-event-native.c could shadow a
goto label.
A compilation error could then occur with gcc 4.7. The variable has
been renamed
to avoid that.
Thank you for your time and valued input.
Signed-off-by: Adrien BAK
---
diff --git a/tools/perf/Makefile.perf b/tools/per
Is it better to introduce a line break than to have a 83-chars
long line?
- in trace-event-scripting.c a struct is declared as extern. Here,
I followed
what was already done for perl/python scripting.
Thank you for your time and valued input.
Signed-off-by: Adrien BAK
---
diff --g
Sorry for the wasted time.
Adrien
On 03/18/2014 07:15 PM, Arnaldo Carvalho de Melo wrote:
Em Tue, Mar 18, 2014 at 05:09:33PM +0100, Adrien BAK escreveu:
This pull request fixes the following issues :
* when passing custom arguments to a script, if those arguments are
not declared within pe
.
These issues are addressed as follows :
* The parse option flag is changed from PARSE_OPT_STOP_AT_NON_OPTION to
PARSE_OPT_KEEP_UNKNOWN
* A new option type is introduce OPT_CALLBACK_FINAL_OPTION, which
effectively
prevents the parsing of all options located after the script.
Signed-off-by: Adrien
7 matches
Mail list logo