Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964898AbWBPUEW (ORCPT ); Thu, 16 Feb 2006 15:04:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964896AbWBPUEW (ORCPT ); Thu, 16 Feb 2006 15:04:22 -0500 Received: from ns.virtualhost.dk ([195.184.98.160]:23839 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id S964894AbWBPUEU (ORCPT ); Thu, 16 Feb 2006 15:04:20 -0500 Date: Thu, 16 Feb 2006 21:01:39 +0100 From: Jens Axboe To: James Bottomley Cc: Russell King , Greg KH , Andrew Morton , Linus Torvalds , linux-kernel@vger.kernel.org, "Brown, Len" , "David S. Miller" , linux-acpi@vger.kernel.org, linux-usb-devel@lists.sourceforge.net, "Yu, Luming" , Ben Castricum , sanjoy@mrao.cam.ac.uk, Helge Hafting , "Carlo E. Prelz" , Gerrit Bruchh?user , Nicolas.Mailhot@LaPoste.net, Jaroslav Kysela , Takashi Iwai , Patrizio Bassi , Bj?rn Nilsson , Andrey Borzenkov , "P. Christeas" , ghrt , jinhong hu , Andrew Vasquez , linux-scsi@vger.kernel.org, Benjamin LaHaise Subject: Re: Linux 2.6.16-rc3 Message-ID: <20060216200138.GA4203@suse.de> References: <20060212190520.244fcaec.akpm@osdl.org> <20060213203800.GC22441@kroah.com> <1139934883.14115.4.camel@mulgrave.il.steeleye.com> <1140054960.3037.5.camel@mulgrave.il.steeleye.com> <20060216171200.GD29443@flint.arm.linux.org.uk> <1140112653.3178.9.camel@mulgrave.il.steeleye.com> <20060216180939.GF29443@flint.arm.linux.org.uk> <1140113671.3178.16.camel@mulgrave.il.steeleye.com> <20060216181803.GG29443@flint.arm.linux.org.uk> <1140116969.3178.24.camel@mulgrave.il.steeleye.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1140116969.3178.24.camel@mulgrave.il.steeleye.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1047 Lines: 29 On Thu, Feb 16 2006, James Bottomley wrote: > On Thu, 2006-02-16 at 18:18 +0000, Russell King wrote: > > Maybe implementing it as a helper function would be the best and > > simplest solution? > > > > static void scsi_release(struct device *dev) > > { > > schedule_release_process(dev, scsi_release_process); > > } > > > > where schedule_release_process() contains more or less what I posted > > in the previous mailing. > > That's almost exactly the execute_in_process_context() API that began > this discussion (and which Andi NAK'd). However, it could possibly be > resurrected with the proviso that the caller has to feed in the > workqueue memory. How would people feel about that? That's what I suggested in the first place as well. I still think it's a good idea, fwiw :) -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/