mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: "Jon Medhurst (Tixy)" <tixy@linaro.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	linux-kernel@vger.kernel.org, Wang Nan <wangnan0@huawei.com>
Subject: Re: What's the correct tree to route kprobes patches through?
Date: Tue, 13 Jan 2015 21:23:07 +0900	[thread overview]
Message-ID: <54B50E2B.2020007@hitachi.com> (raw)
In-Reply-To: <1421086886.18443.23.camel@linaro.org>

(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@hitachi.com



      reply	other threads:[~2015-01-13 12:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 18:21 Jon Medhurst (Tixy)
2015-01-13 12:23 ` Masami Hiramatsu [this message]

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=54B50E2B.2020007@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tixy@linaro.org \
    --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