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-linus][PATCH 0/6] tracing: Fixes and minor clean ups for 5.19
Date: Tue, 12 Jul 2022 16:39:24 -0400 [thread overview]
Message-ID: <20220712203924.060569640@goodmis.org> (raw)
Douglas Anderson (1):
tracing: Fix sleeping while atomic in kdb ftdump
Li kunyu (1):
blk-iocost: tracing: atomic64_read(&ioc->vtime_rate) is assigned an extra semicolon
Steven Rostedt (Google) (1):
ftrace: Be more specific about arch impact when function tracer is enabled
Tiezhu Yang (1):
samples: Use KSYM_NAME_LEN for kprobes
Zheng Yejian (1):
tracing/histograms: Fix memory leak problem
sunliming (1):
fprobe/samples: Make sample_probe static
----
include/trace/events/iocost.h | 2 +-
kernel/trace/Kconfig | 3 ++-
kernel/trace/trace.c | 11 ++++++-----
kernel/trace/trace_events_hist.c | 2 ++
samples/fprobe/fprobe_example.c | 2 +-
samples/kprobes/kprobe_example.c | 5 ++---
samples/kprobes/kretprobe_example.c | 5 ++---
7 files changed, 16 insertions(+), 14 deletions(-)
next reply other threads:[~2022-07-12 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 20:39 Steven Rostedt [this message]
2022-07-12 20:39 ` [for-linus][PATCH 1/6] tracing/histograms: Fix memory leak problem Steven Rostedt
2022-07-12 20:39 ` [for-linus][PATCH 2/6] tracing: Fix sleeping while atomic in kdb ftdump Steven Rostedt
2022-07-12 20:39 ` [for-linus][PATCH 3/6] ftrace: Be more specific about arch impact when function tracer is enabled Steven Rostedt
2022-07-12 20:39 ` [for-linus][PATCH 4/6] blk-iocost: tracing: atomic64_read(&ioc->vtime_rate) is assigned an extra semicolon Steven Rostedt
2022-07-12 20:39 ` [for-linus][PATCH 5/6] fprobe/samples: Make sample_probe static Steven Rostedt
2022-07-12 20:39 ` [for-linus][PATCH 6/6] samples: Use KSYM_NAME_LEN for kprobes 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=20220712203924.060569640@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