erofs: use erofs_inode naming
As Christoph suggested [1], "Why is this called vnode instead of inode? That seems like a rather odd naming for a Linux file system." [1] https://lore.kernel.org/r/20190829101545.GC20598@infradead.org/ Reported-by: Christoph Hellwig <hch@infradead.org> Signed-off-by: Gao Xiang <gaoxiang25@huawei.com> Link: https://lore.kernel.org/r/20190904020912.63925-10-gaoxiang25@huawei.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:

committed by
Greg Kroah-Hartman

parent
1c2dfbf9c2
commit
a5876e24f1
@@ -272,14 +272,14 @@ static inline erofs_off_t iloc(struct erofs_sb_info *sbi, erofs_nid_t nid)
|
||||
}
|
||||
|
||||
/* atomic flag definitions */
|
||||
#define EROFS_V_EA_INITED_BIT 0
|
||||
#define EROFS_V_Z_INITED_BIT 1
|
||||
#define EROFS_I_EA_INITED_BIT 0
|
||||
#define EROFS_I_Z_INITED_BIT 1
|
||||
|
||||
/* bitlock definitions (arranged in reverse order) */
|
||||
#define EROFS_V_BL_XATTR_BIT (BITS_PER_LONG - 1)
|
||||
#define EROFS_V_BL_Z_BIT (BITS_PER_LONG - 2)
|
||||
#define EROFS_I_BL_XATTR_BIT (BITS_PER_LONG - 1)
|
||||
#define EROFS_I_BL_Z_BIT (BITS_PER_LONG - 2)
|
||||
|
||||
struct erofs_vnode {
|
||||
struct erofs_inode {
|
||||
erofs_nid_t nid;
|
||||
|
||||
/* atomic flags (including bitlocks) */
|
||||
@@ -307,8 +307,8 @@ struct erofs_vnode {
|
||||
struct inode vfs_inode;
|
||||
};
|
||||
|
||||
#define EROFS_V(ptr) \
|
||||
container_of(ptr, struct erofs_vnode, vfs_inode)
|
||||
#define EROFS_I(ptr) \
|
||||
container_of(ptr, struct erofs_inode, vfs_inode)
|
||||
|
||||
static inline unsigned long inode_datablocks(struct inode *inode)
|
||||
{
|
||||
|
Reference in New Issue
Block a user