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/4] tracing: Addition of initcall tracing
Date: Sun, 08 Apr 2018 16:10:00 -0400 [thread overview]
Message-ID: <20180408201000.540816094@goodmis.org> (raw)
The last patch keeps initcall_debug working even without
CONFIG_TRACEPOINTS enabled. Nobody appears to be against this
patch set.
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: b0dc52f15e7fe2b973ecfe4f3706f1b35ce3943a
Abderrahmane Benbachir (1):
init, tracing: instrument security and console initcall trace events
Steven Rostedt (VMware) (3):
init, tracing: Add initcall trace events
init, tracing: Have printk come through the trace events for initcall_debug
init: Have initcall_debug still work without CONFIG_TRACEPOINTS
----
include/trace/events/initcall.h | 66 +++++++++++++++++++++++++++++++++
init/main.c | 82 +++++++++++++++++++++++++++++++++--------
kernel/printk/printk.c | 7 +++-
security/security.c | 8 +++-
4 files changed, 145 insertions(+), 18 deletions(-)
create mode 100644 include/trace/events/initcall.h
next reply other threads:[~2018-04-08 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 20:10 Steven Rostedt [this message]
2018-04-08 20:10 ` [for-next][PATCH 1/4] init, tracing: Add initcall trace events Steven Rostedt
2018-04-08 20:10 ` [for-next][PATCH 2/4] init, tracing: instrument security and console " Steven Rostedt
2018-04-08 20:10 ` [for-next][PATCH 3/4] init, tracing: Have printk come through the trace events for initcall_debug Steven Rostedt
2018-04-08 20:10 ` [for-next][PATCH 4/4] init: Have initcall_debug still work without CONFIG_TRACEPOINTS 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=20180408201000.540816094@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.