From: "Jon Medhurst (Tixy)" <tixy@linaro.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
"David S. Miller" <davem@davemloft.net>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Cc: linux-kernel@vger.kernel.org, Wang Nan <wangnan0@huawei.com>
Subject: What's the correct tree to route kprobes patches through?
Date: Mon, 12 Jan 2015 18:21:26 +0000 [thread overview]
Message-ID: <1421086886.18443.23.camel@linaro.org> (raw)
Hi All
I'm wondering what the correct route is for getting kprobes patches into
mainline Linux. In particular I'm interested in a patch from Masami
Hiramatsu [1] which is a dependency for some ARM kprobes work we want to
merge. If acceptable, we could submit that one though the ARM
maintainer's tree with our other work.
[1] http://marc.info/?l=linux-kernel&m=142045769001242&w=2
(kprobes: Pass the original kprobe for preparing optimized kprobe)
Thanks
--
Tixy
next reply other threads:[~2015-01-12 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 18:21 Jon Medhurst (Tixy) [this message]
2015-01-13 12:23 ` Masami Hiramatsu
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=1421086886.18443.23.camel@linaro.org \
--to=tixy@linaro.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=wangnan0@huawei.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
Powered by JetHome