Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757454AbXKFLNk (ORCPT ); Tue, 6 Nov 2007 06:13:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756226AbXKFLNb (ORCPT ); Tue, 6 Nov 2007 06:13:31 -0500 Received: from mx1.redhat.com ([66.187.233.31]:50154 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756278AbXKFLNa (ORCPT ); Tue, 6 Nov 2007 06:13:30 -0500 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <1363.1194347363@redhat.com> References: <1363.1194347363@redhat.com> <20071106022505.f32b1bff.akpm@linux-foundation.org> <20071025163352.5057.59344.stgit@warthog.procyon.org.uk> <20071025163514.5057.4558.stgit@warthog.procyon.org.uk> Cc: dhowells@redhat.com, Andrew Morton , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH 16/31] IGET: Stop FreeVXFS from using iget() and read_inode() [try #5] X-Mailer: MH-E 8.0.3+cvs; nmh 1.2-20070115cvs; GNU Emacs 23.0.50 Date: Tue, 06 Nov 2007 11:13:36 +0000 Message-ID: <1449.1194347616@redhat.com> To: unlisted-recipients:; (no To-header on input) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 660 Lines: 17 David Howells wrote: > > Not completely trivial - the ino_t -> unsigned long conversion needs to be > > propagated fairly widely in there. > > I'll just make it unsigned long. That's what iget() took as the inode number > parameter type, so it can't behave any differently as a first guess. On the other hand, __vxfs_iget() takes ino_t, so that's the right thing to do in this case. David - 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/