From: Ted Ts'o Subject: Re: [PATCH 01/37] e2fsprogs: Read and write full-sized inodes Date: Sun, 4 Sep 2011 10:04:19 -0400 Message-ID: <20110904140419.GE3461@thunk.org> References: <20110901003509.1176.51159.stgit@elm3c44.beaverton.ibm.com> <20110901003517.1176.46651.stgit@elm3c44.beaverton.ibm.com> <0151C905-AE23-4729-92B9-9EAFA44A92FD@dilger.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Darrick J. Wong" , Andreas Dilger , Sunil Mushran , Amir Goldstein , Andi Kleen , Mingming Cao , Joel Becker , "linux-ext4@vger.kernel.org" , Coly Li To: Andreas Dilger Return-path: Received: from li9-11.members.linode.com ([67.18.176.11]:33073 "EHLO test.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753861Ab1IDOE2 (ORCPT ); Sun, 4 Sep 2011 10:04:28 -0400 Content-Disposition: inline In-Reply-To: <0151C905-AE23-4729-92B9-9EAFA44A92FD@dilger.ca> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Sat, Sep 03, 2011 at 12:05:39PM -0600, Andreas Dilger wrote: > Why not just get rid of ext2_inode and replace it with > ext2_inode_large? Less change to the code, and less confusion for > developers. struct ext2_inode_large is there to make sure we don't break ABI compatibility for shared libraries. - Ted