From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "e35.co.us.ibm.com", Issuer "Equifax" (verified OK)) by ozlabs.org (Postfix) with ESMTP id D818EDDEB8 for ; Tue, 26 Jun 2007 13:55:51 +1000 (EST) Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e35.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5Q3tmNk018325 for ; Mon, 25 Jun 2007 23:55:48 -0400 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l5Q3tmDA216114 for ; Mon, 25 Jun 2007 21:55:48 -0600 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l5Q3tluE012968 for ; Mon, 25 Jun 2007 21:55:48 -0600 Date: Tue, 26 Jun 2007 09:29:46 +0530 From: Ananth N Mavinakayanahalli To: Michael Ellerman Subject: Re: [PATCH 1/3] Make struct jprobe.entry a void * Message-ID: <20070626035946.GA20460@in.ibm.com> References: <78935473b1f70c863ab0be7d6cf4bcb04922b20b.1182822366.git.michael@ellerman.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <78935473b1f70c863ab0be7d6cf4bcb04922b20b.1182822366.git.michael@ellerman.id.au> Cc: linux-arch@vger.kernel.org, Andrew Morton , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, anil.s.keshavamurthy@intel.com, linuxppc-dev@ozlabs.org, Christoph Hellwig Reply-To: ananth@in.ibm.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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