From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/2] tracing: A few more updates for 5.20
Date: Mon, 18 Jul 2022 19:17:25 -0400 [thread overview]
Message-ID: <20220718231725.880245563@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 659a93c01063f2fe4aac85938cb52306fe8dd5ac
Masami Hiramatsu (Google) (1):
selftests/kprobe: Update test for no event name syntax error
Steven Rostedt (Google) (1):
tracing: Add example and documentation for new __vstring() macro
----
samples/trace_events/trace-events-sample.c | 14 ++++++++--
samples/trace_events/trace-events-sample.h | 32 +++++++++++++++++++---
.../ftrace/test.d/kprobe/kprobe_syntax_errors.tc | 1 +
3 files changed, 41 insertions(+), 6 deletions(-)
next reply other threads:[~2022-07-18 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 23:17 Steven Rostedt [this message]
2022-07-18 23:17 ` [for-next][PATCH 1/2] tracing: Add example and documentation for new __vstring() macro Steven Rostedt
2022-07-18 23:17 ` [for-next][PATCH 2/2] selftests/kprobe: Update test for no event name syntax error Steven Rostedt
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=20220718231725.880245563@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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