On Thu, Mar 27, 2008 at 11:42 PM, Arnd Bergmann <arnd@xxxxxxxx> wrote: > On Thursday 27 March 2008, Bob Copeland wrote: > If you could avoid the i_state member in omfs_inode_info, you could get > rid of your own inode cache entirely. Your i_state seems to be mostly > write-only, why is it needed in your file system? Err, yeah, it looks to be superfluous. I think it's a relic from when I once did an initialization in omfs_write_inode. Thanks, Bob -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
