On Tue, 2007-06-26 at 09:29 +0530, Ananth N Mavinakayanahalli wrote: > 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. OK, no worries. I guess that's a bit messy to put into a MAINTAINERS entry. cheers -- Michael Ellerman OzLabs, IBM Australia Development Lab wwweb: http://michael.ellerman.id.au phone: +61 2 6212 1183 (tie line 70 21183) We do not inherit the earth from our ancestors, we borrow it from our children. - S.M.A.R.T Person
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- [PATCH 1/3] Make struct jprobe.entry a void *
- From: Michael Ellerman <[email protected]>
- Re: [PATCH 1/3] Make struct jprobe.entry a void *
- From: Ananth N Mavinakayanahalli <[email protected]>
- [PATCH 1/3] Make struct jprobe.entry a void *
- Prev by Date: Re: Patent or not patent a new idea
- Next by Date: Re: [PATCH 1/2] rtc: add rtc-m41t80 driver
- Previous by thread: Re: [PATCH 1/3] Make struct jprobe.entry a void *
- Next by thread: [PATCH] Fix for bad lock balance in Containers
- Index(es):
 |