From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Cc: Ross Zwisler <zwisler@google.com>
Subject: [PATCH] libtraceeval samples: Have samples use traceeval.h and not traceeval-hist.h
Date: Tue, 3 Oct 2023 13:46:07 -0400 [thread overview]
Message-ID: <20231003134607.0cad0947@gandalf.local.home> (raw)
From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
After renaming traceeval-hist.h over to traceeval.h, the sample code still
referenced the traceeval-hist.h. Fix that.
Fixes: 1a6052f926ad ("libtraceeval: Move traceeval-hist.h to traceeval.h")
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
samples/task-eval.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/samples/task-eval.c b/samples/task-eval.c
index 361c4a835f06..4421bd90ad3c 100644
--- a/samples/task-eval.c
+++ b/samples/task-eval.c
@@ -5,7 +5,7 @@
#include <getopt.h>
#include <errno.h>
#include <trace-cmd.h>
-#include <traceeval-hist.h>
+#include <traceeval.h>
static char *argv0;
--
2.40.1
reply other threads:[~2023-10-03 17:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231003134607.0cad0947@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=zwisler@google.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 read-only IMAP folder(s) and NNTP newsgroup(s).