From: David Sterba <dsterba@suse.cz>
To: Geliang Tang <geliangtang@163.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] btrfs: use list_for_each_entry* in check-integrity.c
Date: Tue, 5 Jan 2016 14:50:49 +0100 [thread overview]
Message-ID: <20160105135049.GW4227@twin.jikos.cz> (raw)
In-Reply-To: <8a5a49f737a7eed984c8f92f4684d9a6b761f2f2.1450447999.git.geliangtang@163.com>
On Fri, Dec 18, 2015 at 10:16:59PM +0800, Geliang Tang wrote:
> Use list_for_each_entry*() instead of list_for_each*() to simplify
> the code.
>
> Signed-off-by: Geliang Tang <geliangtang@163.com>
Reviewed-by: David Sterba <dsterba@suse.com>
prev parent reply other threads:[~2016-01-05 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 14:16 [PATCH 1/3] btrfs: use list_for_each_entry* in check-integrity.c Geliang Tang
2015-12-18 14:17 ` [PATCH 2/3] btrfs: use list_for_each_entry_safe in free-space-cache.c Geliang Tang
2015-12-18 14:17 ` [PATCH 3/3] btrfs: use list_for_each_entry* in backref.c Geliang Tang
2015-12-21 15:50 ` [PATCH 3/3 v2] " Geliang Tang
2016-01-05 13:51 ` David Sterba
2016-01-05 13:50 ` [PATCH 2/3] btrfs: use list_for_each_entry_safe in free-space-cache.c David Sterba
2016-01-05 13:50 ` David Sterba [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=20160105135049.GW4227@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=geliangtang@163.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.