stop passing nameidata to ->lookup()
Just the flags; only NFS cares even about that, but there are
legitimate uses for such argument. And getting rid of that
completely would require splitting ->lookup() into a couple
of methods (at least), so let's leave that alone for now...
Signed-off-by:
Al Viro <viro@zeniv.linux.org.uk>
Showing
- Documentation/filesystems/Locking 1 addition, 2 deletionsDocumentation/filesystems/Locking
- Documentation/filesystems/porting 2 additions, 2 deletionsDocumentation/filesystems/porting
- Documentation/filesystems/vfs.txt 1 addition, 1 deletionDocumentation/filesystems/vfs.txt
- fs/9p/v9fs.h 1 addition, 1 deletionfs/9p/v9fs.h
- fs/9p/vfs_inode.c 4 additions, 4 deletionsfs/9p/vfs_inode.c
- fs/9p/vfs_inode_dotl.c 1 addition, 1 deletionfs/9p/vfs_inode_dotl.c
- fs/adfs/dir.c 1 addition, 1 deletionfs/adfs/dir.c
- fs/affs/affs.h 1 addition, 1 deletionfs/affs/affs.h
- fs/affs/namei.c 1 addition, 1 deletionfs/affs/namei.c
- fs/afs/dir.c 2 additions, 2 deletionsfs/afs/dir.c
- fs/afs/mntpt.c 2 additions, 2 deletionsfs/afs/mntpt.c
- fs/autofs4/root.c 2 additions, 2 deletionsfs/autofs4/root.c
- fs/bad_inode.c 1 addition, 1 deletionfs/bad_inode.c
- fs/befs/linuxvfs.c 2 additions, 2 deletionsfs/befs/linuxvfs.c
- fs/bfs/dir.c 1 addition, 1 deletionfs/bfs/dir.c
- fs/btrfs/inode.c 1 addition, 1 deletionfs/btrfs/inode.c
- fs/ceph/dir.c 3 additions, 3 deletionsfs/ceph/dir.c
- fs/cifs/cifsfs.h 1 addition, 1 deletionfs/cifs/cifsfs.h
- fs/cifs/dir.c 2 additions, 2 deletionsfs/cifs/dir.c
- fs/coda/dir.c 2 additions, 2 deletionsfs/coda/dir.c
Loading
Please register or sign in to comment