From: Randy Dunlap <rdunlap@bombadil.infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/inode.c: Fix a rudimentary typo
Date: Fri, 19 Mar 2021 10:54:05 -0700 (PDT) [thread overview]
Message-ID: <b6e29afe-96c2-1016-8a2-40baa542d92@bombadil.infradead.org> (raw)
In-Reply-To: <20210319005342.23795-1-unixbhaskar@gmail.com>
On Fri, 19 Mar 2021, Bhaskar Chowdhury wrote:
> s/funtion/function/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> fs/inode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/inode.c b/fs/inode.c
> index a047ab306f9a..38c2e6b58dc4 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -1423,7 +1423,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,
> --
> 2.26.2
>
>
prev parent reply other threads:[~2021-03-19 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 0:53 [PATCH] fs/inode.c: Fix a rudimentary typo Bhaskar Chowdhury
2021-03-19 17:54 ` Randy Dunlap [this message]
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=b6e29afe-96c2-1016-8a2-40baa542d92@bombadil.infradead.org \
--to=rdunlap@bombadil.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=unixbhaskar@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).