From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org, namhyung@kernel.org
Subject: [PATCH v2 6/8] trace-cmd libtraceevent: Fix type in PRINT_FMT_STING
Date: Wed, 15 Jul 2020 05:30:07 +0300 [thread overview]
Message-ID: <20200715023009.2503879-7-tz.stoyanov@gmail.com> (raw)
In-Reply-To: <20200715023009.2503879-1-tz.stoyanov@gmail.com>
PRINT_FMT_STING -> PRINT_FMT_STRING
Link: https://lore.kernel.org/linux-trace-devel/20200707113138.5a7a27f5@oasis.local.home/T/#md359007fc0883ae3a3088f79b8873a0b568da7bb
Suggested-by: Namhyung Kim <namhyung@kernel.org>
Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
---
lib/traceevent/event-parse-local.h | 2 +-
lib/traceevent/event-parse.c | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/lib/traceevent/event-parse-local.h b/lib/traceevent/event-parse-local.h
index e71296a6..d805a920 100644
--- a/lib/traceevent/event-parse-local.h
+++ b/lib/traceevent/event-parse-local.h
@@ -86,7 +86,7 @@ struct tep_handle {
};
enum tep_print_parse_type {
- PRINT_FMT_STING,
+ PRINT_FMT_STRING,
PRINT_FMT_ARG_DIGIT,
PRINT_FMT_ARG_POINTER,
PRINT_FMT_ARG_STRING,
diff --git a/lib/traceevent/event-parse.c b/lib/traceevent/event-parse.c
index 4de9729c..186fee33 100644
--- a/lib/traceevent/event-parse.c
+++ b/lib/traceevent/event-parse.c
@@ -5659,7 +5659,7 @@ static int parse_arg_format(struct tep_print_parse **parse,
default:
snprintf(print_format, 32, ">%c<", *format);
parse_arg_add(parse, print_format,
- PRINT_FMT_STING, NULL, NULL, 0);
+ PRINT_FMT_STRING, NULL, NULL, 0);
ret++;
return ret;
}
@@ -5711,7 +5711,7 @@ static int parse_arg_string(struct tep_print_parse **parse, const char *format)
ret++;
}
trace_seq_terminate(&s);
- parse_arg_add(parse, s.buffer, PRINT_FMT_STING, NULL, NULL, 0);
+ parse_arg_add(parse, s.buffer, PRINT_FMT_STRING, NULL, NULL, 0);
trace_seq_destroy(&s);
return ret;
@@ -5769,7 +5769,7 @@ static void print_event_cache(struct tep_print_parse *parse, struct trace_seq *s
parse->len_as_arg ? len_arg : -1,
data, size, event, parse->arg);
break;
- case PRINT_FMT_STING:
+ case PRINT_FMT_STRING:
default:
trace_seq_printf(s, "%s", parse->format);
break;
--
2.26.2
next prev parent reply other threads:[~2020-07-15 2:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 2:30 [PATCH v2 0/8] Few libtraceeevnt fixes, suggested Namhyung Kim Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 1/8] trace-cmd libtraceevent: Document tep_load_plugins_hook() Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 2/8] trace-cmd libtraceevent: Handle strdup() error in parse_option_name() Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 3/8] trace-cmd libtraceevent: Fix typo in tep_plugin_add_option() description Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 4/8] trace-cmd libtraceevent: Improve error handling of tep_plugin_add_option() API Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 5/8] trace-cmd libtraceevent: Fix broken indentation in parse_ip4_print_args() Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` Tzvetomir Stoyanov (VMware) [this message]
2020-07-15 2:30 ` [PATCH v2 7/8] trace-cmd libtraceevent: Fix description of tep_add_plugin_path() API Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 8/8] trace-cmd libtraceevent: Handle possible strdup() error in " Tzvetomir Stoyanov (VMware)
2020-07-15 2:36 ` [PATCH v2 0/8] Few libtraceeevnt fixes, suggested Namhyung Kim Steven Rostedt
2020-07-15 4:12 ` Tzvetomir Stoyanov
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=20200715023009.2503879-7-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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).