From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] fs-private data in struct block_device Date: Fri, 2 Jan 2004 09:48:42 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20040102084842.GA10795@lst.de> References: <20040101164219.GB654@lst.de> <20040101151017.3f7bc407.akpm@osdl.org> <20040102024317.GA3851@gtf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , viro@parcelfarce.linux.theplanet.co.uk, linux-fsdevel@vger.kernel.org Return-path: Received: from verein.lst.de ([212.34.189.10]:55996 "EHLO mail.lst.de") by vger.kernel.org with ESMTP id S265437AbUABIsv (ORCPT ); Fri, 2 Jan 2004 03:48:51 -0500 To: Jeff Garzik Content-Disposition: inline In-Reply-To: <20040102024317.GA3851@gtf.org> List-Id: linux-fsdevel.vger.kernel.org On Thu, Jan 01, 2004 at 09:43:17PM -0500, Jeff Garzik wrote: > It looks like the standard normally-a-pointer thing that's completely > managed opaquely to the block device layer. In fact, I actually prefer > that these be (void*) unless there is a common use as an integer. The XFS usage would be as int (actually as boolean)