[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <54B50E2B.2020007@hitachi.com>
Date: Tue, 13 Jan 2015 21:23:07 +0900
From: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
To: "Jon Medhurst (Tixy)" <tixy@...aro.org>
Cc: "David S. Miller" <davem@...emloft.net>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
linux-kernel@...r.kernel.org, Wang Nan <wangnan0@...wei.com>
Subject: Re: What's the correct tree to route kprobes patches through?
(2015/01/13 3:21), Jon Medhurst (Tixy) wrote:
> 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.
I'm OK to merge that patch via ARM's tree. Fortunately, that patch is
just a minor change. So I think it works.
Usually only generic or x86-dependent kprobes patches are upstreamed via
tip tree, and arch-dependent part of kprobes patches should go through arch
specific tree.
Of course I can also provide a new git repo for kprobes on kernel.org. :)
(But still which repo I should send a pull request is a question...)
Thank you,
>
> [1] http://marc.info/?l=linux-kernel&m=142045769001242&w=2
> (kprobes: Pass the original kprobe for preparing optimized kprobe)
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@...achi.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists