LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Ingo Molnar <mingo@kernel.org>,
"Naveen N . Rao" <naveen.n.rao@linux.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S . Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kprobes: Fix to init kprobes in subsys_initcall
Date: Wed, 12 Jun 2019 09:47:29 -0400 [thread overview]
Message-ID: <20190612094729.40106a28@gandalf.local.home> (raw)
In-Reply-To: <20190612165947.ba696696dac0faa3aa35a501@kernel.org>
On Wed, 12 Jun 2019 16:59:47 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Hi Steve,
>
> Could you pick this to your ftrace/core branch?
"core" or should this go to "urgent"? The difference is that core is
scheduled for the next merge window, and urgent is for the rc releases
(ie. bug fixes).
-- Steve
>
> Thank you,
>
>
next prev parent reply other threads:[~2019-06-12 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 8:32 [PATCH v2 0/2] Enable new kprobe event at boot Masami Hiramatsu
2019-05-22 8:32 ` [PATCH v2 1/2] kprobes: Initialize kprobes at postcore_initcall Masami Hiramatsu
2019-05-22 8:32 ` [PATCH v2 2/2] tracing/kprobe: Add kprobe_event= boot parameter Masami Hiramatsu
2019-05-28 12:23 ` Anders Roxell
2019-05-28 12:36 ` Steven Rostedt
2019-05-28 13:39 ` Anders Roxell
2019-06-03 11:52 ` Masami Hiramatsu
2019-06-03 12:41 ` Masami Hiramatsu
2019-06-03 13:04 ` [PATCH] kprobes: Fix to init kprobes in subsys_initcall Masami Hiramatsu
2019-06-03 20:33 ` Anders Roxell
2019-06-04 9:06 ` Steven Rostedt
2019-06-04 15:56 ` Masami Hiramatsu
2019-06-12 7:59 ` Masami Hiramatsu
2019-06-12 13:47 ` Steven Rostedt [this message]
2019-06-13 7:08 ` Masami Hiramatsu
2019-06-14 20:38 ` 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=20190612094729.40106a28@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=anders.roxell@linaro.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--subject='Re: [PATCH] kprobes: Fix to init kprobes in subsys_initcall' \
/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
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).