From: Kirill Smelkov Date: Thu, 14 Aug 2014 11:25:10 +0000 (+0400) Subject: vfs: fix typo in s_op->alloc_inode() documentation X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=4e07ad6406d8137cc5aa1317568408c461ee8ce8;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git vfs: fix typo in s_op->alloc_inode() documentation The function which calls s_op->alloc_inode() is not inode_alloc(), but instead alloc_inode() which lives in fs/inode.c . The typo was there from the beginning from 5ea626aa (VFS: update documentation, 2005) - there was no standalone inode_alloc() for the whole kernel history. Cc: Pekka Enberg Signed-off-by: Kirill Smelkov Signed-off-by: Al Viro --- diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt index 61d65cc65c54..02a766ca2f69 100644 --- a/Documentation/filesystems/vfs.txt +++ b/Documentation/filesystems/vfs.txt @@ -237,7 +237,7 @@ noted. This means that most methods can block safely. All methods are only called from a process context (i.e. not from an interrupt handler or bottom half). - alloc_inode: this method is called by inode_alloc() to allocate memory + alloc_inode: this method is called by alloc_inode() to allocate memory for struct inode and initialize it. If this function is not defined, a simple 'struct inode' is allocated. Normally alloc_inode will be used to allocate a larger structure which