All of lore.kernel.org
 help / color / mirror / Atom feed
From: lijian_8010a29@163.com
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	lijian <lijian@yulong.com>
Subject: [PATCH] fs: inode: Fix a typo
Date: Mon,  7 Jun 2021 14:32:26 +0800	[thread overview]
Message-ID: <20210607063226.205255-1-lijian_8010a29@163.com> (raw)

From: lijian <lijian@yulong.com>

Change 'funtion' to 'function', and
change 'priviledges' to 'privileges'.

Signed-off-by: lijian <lijian@yulong.com>
---
 fs/inode.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/inode.c b/fs/inode.c
index c93500d84264..fd00657184f2 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -1429,7 +1429,7 @@ EXPORT_SYMBOL(ilookup);
  * function must never block --- find_inode() can block in
  * __wait_on_freeing_inode() --- or when the caller can not increment
  * the reference count because the resulting iput() might cause an
- * inode eviction.  The tradeoff is that the @match funtion must be
+ * inode eviction.  The tradeoff is that the @match function must be
  * very carefully implemented.
  */
 struct inode *find_inode_nowait(struct super_block *sb,
@@ -1926,7 +1926,7 @@ static int __remove_privs(struct user_namespace *mnt_userns,
 }
 
 /*
- * Remove special file priviledges (suid, capabilities) when file is written
+ * Remove special file privileges (suid, capabilities) when file is written
  * to or truncated.
  */
 int file_remove_privs(struct file *file)
-- 
2.25.1


                 reply	other threads:[~2021-06-07  6:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210607063226.205255-1-lijian_8010a29@163.com \
    --to=lijian_8010a29@163.com \
    --cc=lijian@yulong.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.