Fix checkpatch errors:

"ERROR: return is not a function, parentheses are not required"

Cc: Andrew Morton <[email protected]>
Signed-off-by: Fabian Frederick <[email protected]>
---
 fs/efs/namei.c | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/fs/efs/namei.c b/fs/efs/namei.c
index 356c044..bbee8f0 100644
--- a/fs/efs/namei.c
+++ b/fs/efs/namei.c
@@ -12,7 +12,8 @@
 #include "efs.h"
 
 
-static efs_ino_t efs_find_entry(struct inode *inode, const char *name, int 
len) {
+static efs_ino_t efs_find_entry(struct inode *inode, const char *name, int len)
+{
        struct buffer_head *bh;
 
        int                     slot, namelen;
@@ -40,10 +41,10 @@ static efs_ino_t efs_find_entry(struct inode *inode, const 
char *name, int len)
                if (be16_to_cpu(dirblock->magic) != EFS_DIRBLK_MAGIC) {
                        pr_err("%s(): invalid directory block\n", __func__);
                        brelse(bh);
-                       return(0);
+                       return 0;
                }
 
-               for(slot = 0; slot < dirblock->slots; slot++) {
+               for (slot = 0; slot < dirblock->slots; slot++) {
                        dirslot  = (struct efs_dentry *) (((char *) bh->b_data) 
+ EFS_SLOTAT(dirblock, slot));
 
                        namelen  = dirslot->namelen;
@@ -52,12 +53,12 @@ static efs_ino_t efs_find_entry(struct inode *inode, const 
char *name, int len)
                        if ((namelen == len) && (!memcmp(name, nameptr, len))) {
                                inodenum = be32_to_cpu(dirslot->inode);
                                brelse(bh);
-                               return(inodenum);
+                               return inodenum;
                        }
                }
                brelse(bh);
        }
-       return(0);
+       return 0;
 }
 
 struct dentry *efs_lookup(struct inode *dir, struct dentry *dentry, unsigned 
int flags)
-- 
1.8.4.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to