linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Xiaofeng Cao <cxfcosmos@gmail.com>, viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Xiaofeng Cao <caoxiaofeng@yulong.com>
Subject: Re: [PATCH v2] fs/dcache: fix typos and sentence disorder
Date: Tue, 23 Mar 2021 10:42:14 -0700	[thread overview]
Message-ID: <36a2d11d-8413-f4a7-9f69-fe513d26c4aa@infradead.org> (raw)
In-Reply-To: <20210323065245.15083-1-caoxiaofeng@yulong.com>

On 3/22/21 11:52 PM, Xiaofeng Cao wrote:
> change 'sould' to 'should'
> change 'colocated' to 'co-located'
> change 'talke' to 'take'
> reorganize sentence
> 
> Signed-off-by: Xiaofeng Cao <caoxiaofeng@yulong.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

> ---
> v2:change 'colocated' to 'co-located' instead of 'collocated'
>  fs/dcache.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/dcache.c b/fs/dcache.c
> index 7d24ff7eb206..c23834334314 100644
> --- a/fs/dcache.c
> +++ b/fs/dcache.c
> @@ -741,7 +741,7 @@ static inline bool fast_dput(struct dentry *dentry)
>  	unsigned int d_flags;
>  
>  	/*
> -	 * If we have a d_op->d_delete() operation, we sould not
> +	 * If we have a d_op->d_delete() operation, we should not
>  	 * let the dentry count go to zero, so use "put_or_lock".
>  	 */
>  	if (unlikely(dentry->d_flags & DCACHE_OP_DELETE))
> @@ -1053,7 +1053,7 @@ struct dentry *d_find_alias_rcu(struct inode *inode)
>  	struct dentry *de = NULL;
>  
>  	spin_lock(&inode->i_lock);
> -	// ->i_dentry and ->i_rcu are colocated, but the latter won't be
> +	// ->i_dentry and ->i_rcu are co-located, but the latter won't be
>  	// used without having I_FREEING set, which means no aliases left
>  	if (likely(!(inode->i_state & I_FREEING) && !hlist_empty(l))) {
>  		if (S_ISDIR(inode->i_mode)) {
> @@ -1297,7 +1297,7 @@ void shrink_dcache_sb(struct super_block *sb)
>  EXPORT_SYMBOL(shrink_dcache_sb);
>  
>  /**
> - * enum d_walk_ret - action to talke during tree walk
> + * enum d_walk_ret - action to take during tree walk
>   * @D_WALK_CONTINUE:	contrinue walk
>   * @D_WALK_QUIT:	quit walk
>   * @D_WALK_NORETRY:	quit when retry is needed
> @@ -2156,8 +2156,8 @@ EXPORT_SYMBOL(d_obtain_alias);
>   *
>   * On successful return, the reference to the inode has been transferred
>   * to the dentry.  In case of an error the reference on the inode is
> - * released.  A %NULL or IS_ERR inode may be passed in and will be the
> - * error will be propagate to the return value, with a %NULL @inode
> + * released.  A %NULL or IS_ERR inode may be passed in and the error will
> + * be propagated to the return value, with a %NULL @inode
>   * replaced by ERR_PTR(-ESTALE).
>   */
>  struct dentry *d_obtain_root(struct inode *inode)
> 


-- 
~Randy


      reply	other threads:[~2021-03-23 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23  6:52 [PATCH v2] fs/dcache: fix typos and sentence disorder Xiaofeng Cao
2021-03-23 17:42 ` 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=36a2d11d-8413-f4a7-9f69-fe513d26c4aa@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=caoxiaofeng@yulong.com \
    --cc=cxfcosmos@gmail.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 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).