All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhong jiang <zhongjiang@huawei.com>
To: <dsterba@suse.cz>, Omar Sandoval <osandov@osandov.com>,
	<dsterba@suse.com>, <jbacik@fb.com>, <clm@fb.com>,
	<linux-btrfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] btrfs: list usage cleanup
Date: Thu, 4 Oct 2018 11:25:44 +0800	[thread overview]
Message-ID: <5BB58838.7080202@huawei.com> (raw)
In-Reply-To: <20181001164831.GS3255@twin.jikos.cz>

On 2018/10/2 0:48, David Sterba wrote:
> On Thu, Sep 27, 2018 at 11:47:04AM -0700, Omar Sandoval wrote:
>> On Wed, Sep 26, 2018 at 04:35:45PM +0800, zhong jiang wrote:
>>> Trival cleanup, list_move_tail will implement the same function that
>>> list_del() + list_add_tail() will do. hence just replace them.
>>>
>>> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
>>> ---
>>>  fs/btrfs/send.c | 3 +--
>>>  1 file changed, 1 insertion(+), 2 deletions(-)
>>>
>>> diff --git a/fs/btrfs/send.c b/fs/btrfs/send.c
>>> index 094cc144..d87f416 100644
>>> --- a/fs/btrfs/send.c
>>> +++ b/fs/btrfs/send.c
>>> @@ -2075,8 +2075,7 @@ static struct name_cache_entry *name_cache_search(struct send_ctx *sctx,
>>>   */
>>>  static void name_cache_used(struct send_ctx *sctx, struct name_cache_entry *nce)
>>>  {
>>> -	list_del(&nce->list);
>>> -	list_add_tail(&nce->list, &sctx->name_cache_list);
>>> +	list_move_tail(&nce->list, &sctx->name_cache_list);
>>>  }
>> At that point do we even need such a trivial helper, considering that
>> this is only called in one place?
> Fair point and trivial one-line helpers are on the cleanup todo list.
> The exception is when the actual helper implementation is obscuring the
> semantics and the helper is used in many places so it's not practical to
> add a comment everywhere. But it's not the case here.
>
> Zhong Jiang, please update the patch and resend, thanks.
Will add a comment here and resend in v2.

Thanks,
zhong jiang
> .
>



      reply	other threads:[~2018-10-04  3:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26  8:35 [PATCH] btrfs: list usage cleanup zhong jiang
2018-09-26  8:53 ` Nikolay Borisov
2018-09-27  9:07 ` David Sterba
2018-09-27 18:47 ` Omar Sandoval
2018-10-01 16:48   ` David Sterba
2018-10-04  3:25     ` zhong jiang [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=5BB58838.7080202@huawei.com \
    --to=zhongjiang@huawei.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osandov@osandov.com \
    /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.