From: "Theodore Ts'o" <tytso@mit.edu>
To: Daejun Park <daejun7.park@samsung.com>
Cc: harshad shirwadkar <harshadshirwadkar@gmail.com>,
"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH v2] ext4: Change list_for_each* to list_for_each_entry*
Date: Wed, 3 Feb 2021 00:05:23 -0500 [thread overview]
Message-ID: <YBovEwunfCV23Rxe@mit.edu> (raw)
In-Reply-To: <20210111013726epcms2p4579ae56040d7043db785bf0d0a785dc7@epcms2p4>
On Mon, Jan 11, 2021 at 10:37:26AM +0900, Daejun Park wrote:
> In the fast_commit.c, list_for_each* + list_entry can be changed to
> list_for_each_entry*. It reduces number of variables and lines.
>
> Signed-off-by: Daejun Park <daejun7.park@samsung.com>
Thanks, applied.
- Ted
prev parent reply other threads:[~2021-02-03 5:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210111013726epcms2p4579ae56040d7043db785bf0d0a785dc7@epcms2p4>
2021-01-11 1:37 ` [PATCH v2] ext4: Change list_for_each* to list_for_each_entry* Daejun Park
2021-02-03 5:05 ` Theodore Ts'o [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=YBovEwunfCV23Rxe@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=daejun7.park@samsung.com \
--cc=harshadshirwadkar@gmail.com \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox