From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
linux-ia64@vger.kernel.org, linux-arch@vger.kernel.org,
Andrew Morton <akpm@osdl.org>, Christoph Hellwig <hch@lst.de>,
anil.s.keshavamurthy@intel.com
Subject: Re: [PATCH 1/3] Make struct jprobe.entry a void *
Date: Tue, 26 Jun 2007 09:29:46 +0530 [thread overview]
Message-ID: <20070626035946.GA20460@in.ibm.com> (raw)
In-Reply-To: <78935473b1f70c863ab0be7d6cf4bcb04922b20b.1182822366.git.michael@ellerman.id.au>
On Tue, Jun 26, 2007 at 11:48:50AM +1000, Michael Ellerman wrote:
> ---
>
> It isn't obvious where kprobes patches should go, is anyone "the" maintainer?
> Instead I've just sent this to everyone who'd touched the code lately, or
> might be otherwise interested.
There isn't a single maintainer for the kprobes infrastructure as it
contains quite a bit of low level arch specific code. The working model
currently is that the patches are sent to lkml with a cc to the
maintainers listed, as you've rightly done.
Ananth
WARNING: multiple messages have this Message-ID (diff)
From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
linux-ia64@vger.kernel.org, linux-arch@vger.kernel.org,
Andrew Morton <akpm@osdl.org>, Christoph Hellwig <hch@lst.de>,
anil.s.keshavamurthy@intel.com
Subject: Re: [PATCH 1/3] Make struct jprobe.entry a void *
Date: Tue, 26 Jun 2007 03:56:17 +0000 [thread overview]
Message-ID: <20070626035946.GA20460@in.ibm.com> (raw)
In-Reply-To: <78935473b1f70c863ab0be7d6cf4bcb04922b20b.1182822366.git.michael@ellerman.id.au>
On Tue, Jun 26, 2007 at 11:48:50AM +1000, Michael Ellerman wrote:
> ---
>
> It isn't obvious where kprobes patches should go, is anyone "the" maintainer?
> Instead I've just sent this to everyone who'd touched the code lately, or
> might be otherwise interested.
There isn't a single maintainer for the kprobes infrastructure as it
contains quite a bit of low level arch specific code. The working model
currently is that the patches are sent to lkml with a cc to the
maintainers listed, as you've rightly done.
Ananth
WARNING: multiple messages have this Message-ID (diff)
From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linux-arch@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
anil.s.keshavamurthy@intel.com, linuxppc-dev@ozlabs.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/3] Make struct jprobe.entry a void *
Date: Tue, 26 Jun 2007 09:29:46 +0530 [thread overview]
Message-ID: <20070626035946.GA20460@in.ibm.com> (raw)
In-Reply-To: <78935473b1f70c863ab0be7d6cf4bcb04922b20b.1182822366.git.michael@ellerman.id.au>
On Tue, Jun 26, 2007 at 11:48:50AM +1000, Michael Ellerman wrote:
> ---
>
> It isn't obvious where kprobes patches should go, is anyone "the" maintainer?
> Instead I've just sent this to everyone who'd touched the code lately, or
> might be otherwise interested.
There isn't a single maintainer for the kprobes infrastructure as it
contains quite a bit of low level arch specific code. The working model
currently is that the patches are sent to lkml with a cc to the
maintainers listed, as you've rightly done.
Ananth
WARNING: multiple messages have this Message-ID (diff)
From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: <linux-kernel@vger.kernel.org>, <linuxppc-dev@ozlabs.org>,
<linux-ia64@vger.kernel.org>, <linux-arch@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Christoph Hellwig <hch@lst.de>,
<anil.s.keshavamurthy@intel.com>
Subject: Re: [PATCH 1/3] Make struct jprobe.entry a void *
Date: Tue, 26 Jun 2007 09:29:46 +0530 [thread overview]
Message-ID: <20070626035946.GA20460@in.ibm.com> (raw)
In-Reply-To: <78935473b1f70c863ab0be7d6cf4bcb04922b20b.1182822366.git.michael@ellerman.id.au>
On Tue, Jun 26, 2007 at 11:48:50AM +1000, Michael Ellerman wrote:
> ---
>
> It isn't obvious where kprobes patches should go, is anyone "the" maintainer?
> Instead I've just sent this to everyone who'd touched the code lately, or
> might be otherwise interested.
There isn't a single maintainer for the kprobes infrastructure as it
contains quite a bit of low level arch specific code. The working model
currently is that the patches are sent to lkml with a cc to the
maintainers listed, as you've rightly done.
Ananth
next prev parent reply other threads:[~2007-06-26 3:55 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 1:48 [PATCH 1/3] Make struct jprobe.entry a void * Michael Ellerman
2007-06-26 1:48 ` Michael Ellerman
2007-06-26 1:48 ` Michael Ellerman
2007-06-26 1:48 ` Michael Ellerman
2007-06-26 1:48 ` [PATCH 3/3] Make jprobes a little safer for users Michael Ellerman
2007-06-26 1:48 ` Michael Ellerman
2007-06-26 1:48 ` Michael Ellerman
2007-06-26 1:48 ` Michael Ellerman
2007-06-26 2:00 ` Andrew Morton
2007-06-26 2:00 ` Andrew Morton
2007-06-26 2:00 ` Andrew Morton
2007-06-26 2:00 ` Andrew Morton
2007-06-26 2:06 ` Michael Ellerman
2007-06-26 2:06 ` Michael Ellerman
2007-06-26 2:06 ` Michael Ellerman
2007-06-26 2:24 ` [PATCH 1/1] Add a prototype for arch_deref_entry_point() Michael Ellerman
2007-06-26 5:53 ` [PATCH 3/3] Make jprobes a little safer for users Christoph Hellwig
2007-06-26 5:53 ` Christoph Hellwig
2007-06-26 5:53 ` Christoph Hellwig
2007-06-26 6:03 ` Michael Ellerman
2007-06-26 6:03 ` Michael Ellerman
2007-06-26 6:03 ` Michael Ellerman
2007-06-26 6:51 ` Andrew Morton
2007-06-26 6:51 ` Andrew Morton
2007-06-26 6:51 ` Andrew Morton
2007-06-26 6:19 ` Abhishek Sagar
2007-06-26 6:31 ` Abhishek Sagar
2007-06-26 6:19 ` Abhishek Sagar
2007-06-26 6:34 ` Michael Ellerman
2007-06-26 6:34 ` Michael Ellerman
2007-06-26 6:34 ` Michael Ellerman
2007-06-26 7:54 ` Abhishek Sagar
2007-06-26 7:55 ` Abhishek Sagar
2007-06-26 7:54 ` Abhishek Sagar
2007-06-26 1:48 ` [PATCH 2/3] Remove JPROBE_ENTRY() Michael Ellerman
2007-06-26 1:48 ` Michael Ellerman
2007-06-26 1:48 ` Michael Ellerman
2007-06-26 1:48 ` Michael Ellerman
2007-06-26 5:52 ` Christoph Hellwig
2007-06-26 5:52 ` Christoph Hellwig
2007-06-26 5:52 ` Christoph Hellwig
2007-06-26 3:48 ` [PATCH 1/3] Make struct jprobe.entry a void * Ananth N Mavinakayanahalli
2007-06-26 3:51 ` Ananth N Mavinakayanahalli
2007-06-26 3:51 ` Ananth N Mavinakayanahalli
2007-06-26 3:51 ` Ananth N Mavinakayanahalli
2007-06-26 3:56 ` Ananth N Mavinakayanahalli [this message]
2007-06-26 3:59 ` Ananth N Mavinakayanahalli
2007-06-26 3:59 ` Ananth N Mavinakayanahalli
2007-06-26 3:59 ` Ananth N Mavinakayanahalli
2007-06-26 4:35 ` Michael Ellerman
2007-06-26 4:35 ` Michael Ellerman
2007-06-26 4:35 ` Michael Ellerman
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=20070626035946.GA20460@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=akpm@osdl.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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.