From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mtagate4.de.ibm.com ([195.212.29.153]) by pentafluge.infradead.org with esmtps (Exim 4.63 #1 (Red Hat Linux)) id 1IHw04-000212-Sj for linux-mtd@lists.infradead.org; Mon, 06 Aug 2007 07:23:34 +0100 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate4.de.ibm.com (8.13.8/8.13.8) with ESMTP id l766NOls120628 for ; Mon, 6 Aug 2007 06:23:24 GMT Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.4) with ESMTP id l766NOOq1298546 for ; Mon, 6 Aug 2007 08:23:24 +0200 Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l766NKvd005428 for ; Mon, 6 Aug 2007 08:23:20 +0200 Message-ID: <46B6BE56.8060409@de.ibm.com> Date: Mon, 06 Aug 2007 08:23:18 +0200 From: Carsten Otte MIME-Version: 1.0 To: David Woodhouse Subject: Re: [PATCH][MTD] mtdpart.c: allow other drivers to get physical address of partition References: <6934efce0707261704p5e46e238i5b7ee433fc4f5bda@mail.gmail.com> <1185882932.3083.98.camel@pmac.infradead.org> <6934efce0707311255k57b60d59y5a07d2812b37ca1a@mail.gmail.com> <20070801121800.GB2747@lazybastard.org> <46B083B3.80009@de.ibm.com> <6934efce0708011337g32169212v329c778bb7700aea@mail.gmail.com> <46B18D89.1010207@de.ibm.com> <6934efce0708021455h29c9151aw7aab2245df0062e5@mail.gmail.com> <1186146543.2931.82.camel@pmac.infradead.org> In-Reply-To: <1186146543.2931.82.camel@pmac.infradead.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: carsteno@de.ibm.com, dhowells , =?ISO-8859-1?Q?J=F6rn_Engel?= , "linux-mtd@lists.infradead.org" Reply-To: carsteno@de.ibm.com List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , David Woodhouse wrote: > Alternatively, just wait for the chip to become available. Or increment > a count of 'waiters' and only interrupt the erase when there are a > certain number of people waiting. Sounds reasonable to me. Maybe we should even think about the block device plug approach: set up a timer when the first reader shows up, and suspend when either a certain amount of readers shows up or the timer has run down.