linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vyacheslav Dubeyko <slava@dubeyko.com>
To: Geliang Tang <geliangtang@163.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hfs: use list_for_each_entry in hfs_cat_delete
Date: Tue, 08 Dec 2015 09:12:00 -0800	[thread overview]
Message-ID: <1449594720.2689.1.camel@ubuntu-slavad-14.04> (raw)
In-Reply-To: <bac4e5839dda9d7e87bd589e6761f1e43a609aef.1449588068.git.geliangtang@163.com>

On Tue, 2015-12-08 at 23:22 +0800, Geliang Tang wrote:
> Use list_for_each_entry() instead of list_for_each() to simplify
> the code.
> 

Looks good.

Reviewed-by: Vyacheslav Dubeyko <slava@dubeyko.com>

Thanks,
Vyacheslav Dubeyko.

> Signed-off-by: Geliang Tang <geliangtang@163.com>
> ---
>  fs/hfs/catalog.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/hfs/catalog.c b/fs/hfs/catalog.c
> index db458ee..1eb5d41 100644
> --- a/fs/hfs/catalog.c
> +++ b/fs/hfs/catalog.c
> @@ -214,7 +214,7 @@ int hfs_cat_delete(u32 cnid, struct inode *dir, struct qstr *str)
>  {
>  	struct super_block *sb;
>  	struct hfs_find_data fd;
> -	struct list_head *pos;
> +	struct hfs_readdir_data *rd;
>  	int res, type;
>  
>  	hfs_dbg(CAT_MOD, "delete_cat: %s,%u\n", str ? str->name : NULL, cnid);
> @@ -240,9 +240,7 @@ int hfs_cat_delete(u32 cnid, struct inode *dir, struct qstr *str)
>  		}
>  	}
>  
> -	list_for_each(pos, &HFS_I(dir)->open_dir_list) {
> -		struct hfs_readdir_data *rd =
> -			list_entry(pos, struct hfs_readdir_data, list);
> +	list_for_each_entry(rd, &HFS_I(dir)->open_dir_list, list) {
>  		if (fd.tree->keycmp(fd.search_key, (void *)&rd->key) < 0)
>  			rd->file->f_pos--;
>  	}



      reply	other threads:[~2015-12-08 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 15:22 [PATCH] hfs: use list_for_each_entry in hfs_cat_delete Geliang Tang
2015-12-08 17:12 ` Vyacheslav Dubeyko [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=1449594720.2689.1.camel@ubuntu-slavad-14.04 \
    --to=slava@dubeyko.com \
    --cc=akpm@linux-foundation.org \
    --cc=geliangtang@163.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    /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).