From: Shaohua Li <shli@kernel.org>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: NeilBrown <nfbrown@novell.com>,
Eyal Lebedinsky <eyal@eyal.emu.id.au>,
linux-raid@vger.kernel.org, kernelpatch@126.com
Subject: Re: [PATCH] md: make the code more readable in the for-loop
Date: Tue, 10 May 2016 17:29:36 -0700 [thread overview]
Message-ID: <20160511002936.GA127453@kernel.org> (raw)
In-Reply-To: <wrfjd1ovrmdp.fsf@redhat.com>
On Mon, May 09, 2016 at 04:45:38PM -0400, Jes Sorensen wrote:
> NeilBrown <nfbrown@novell.com> writes:
> > On Mon, May 09 2016, Shaohua Li wrote:
> >
> >> On Mon, May 09, 2016 at 09:33:39AM +1000, Eyal Lebedinsky wrote:
> >>> I do not see how this change makes it clearer. The original form is
> >>> actually a very common and clear
> >>> scan an array in reverse order
> >>
> >> People always have different opinions for this stuff. When I read '--j' or
> >> 'j--', I always think extra time what the value of j is. So for me the change
> >> actually makes the code more readable :)
> >
> > If the goal is to make the code more readable, you may as well make it:
> >
> > for (j = 0; i < ->raid_disk; j++)
> >
> > That will be clearer to most people than the current code, which I don't
> > think is very much clearer than the original (maybe a little bit).
>
> I agree - I had to read the updated version multiple times to convince
> myself it was doing the same thing as the original.
ok, droped the patch. If Tiezhu Yang is willing to post a new one as neil
suggested, I'll still apply. To be honest I hate the 'j--' and check 'j' stuff.
Thanks,
Shaohua
prev parent reply other threads:[~2016-05-11 0:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 12:56 [PATCH] md: make the code more readable in the for-loop Tiezhu Yang
2016-05-08 23:03 ` Shaohua Li
2016-05-08 23:33 ` Eyal Lebedinsky
2016-05-09 3:53 ` Shaohua Li
2016-05-09 6:31 ` NeilBrown
2016-05-09 20:45 ` Jes Sorensen
2016-05-11 0:29 ` Shaohua Li [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=20160511002936.GA127453@kernel.org \
--to=shli@kernel.org \
--cc=Jes.Sorensen@redhat.com \
--cc=eyal@eyal.emu.id.au \
--cc=kernelpatch@126.com \
--cc=linux-raid@vger.kernel.org \
--cc=nfbrown@novell.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 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).