A variable declaration landed one function higher than intended,
leading to an unused variable warning for configurations with
YAFFS_USE_DIR_ITERATE=y and a build failure for configurations
with the same being unset.

Fixes: "yaffs: Fix build failure by handling inode i_version with proper atomic 
API"
Signed-off-by: Paul Gortmaker <[email protected]>

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index 598ecd57a0ed..3ffdc0129637 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -1826,7 +1826,6 @@ static int yaffs_iterate(struct file *f, struct 
dir_context *dc)
        int ret_val = 0;
 
        char name[YAFFS_MAX_NAME_LENGTH + 1];
-       u64 i_version;
 
        obj = yaffs_dentry_to_obj(Y_GET_DENTRY(f));
        dev = obj->my_dev;
@@ -1898,6 +1897,7 @@ static int yaffs_readdir(struct file *f, void *dirent, 
filldir_t filldir)
        unsigned long offset, curoffs;
        struct yaffs_obj *l;
        int ret_val = 0;
+       u64 i_version;
 
        char name[YAFFS_MAX_NAME_LENGTH + 1];
 
-- 
2.7.4

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8626): 
https://lists.yoctoproject.org/g/linux-yocto/message/8626
Mute This Topic: https://lists.yoctoproject.org/mt/73379932/21656
Group Owner: [email protected]
Unsubscribe: 
https://lists.yoctoproject.org/g/linux-yocto/leave/6687884/624485779/xyzzy  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to