From: Michael Ellerman <mpe@ellerman.id.au>
To: Robert Jennings <rcj4747@gmail.com>
Cc: linux-kernel@vger.kernel.org, Julia Lawall <julia.lawall@lip6.fr>,
Himangi Saraogi <himangi774@gmail.com>,
Brian King <brking@linux.vnet.ibm.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/pseries: Drop unnecessary continue
Date: Mon, 25 Aug 2014 14:16:18 +1000 [thread overview]
Message-ID: <1408940178.7941.3.camel@concordia> (raw)
In-Reply-To: <53F61586.3000107@gmail.com>
On Thu, 2014-08-21 at 10:51 -0500, Robert Jennings wrote:
> On 08/20/2014 11:41 PM, Michael Ellerman wrote:
> > On Wed, 2014-08-13 at 14:48 +0530, Himangi Saraogi wrote:
> >> Continue is not needed at the bottom of a loop.
> >
> > True.
> >
> > I wonder though, is the code trying to continue to the outer loop?
> > I stared at it for a minute but it wasn't obvious.
> >
> > I wonder if Robert still remembers?
>
> I don't recall what the intent was here. Can't believe that it's been
> almost 5 years since I wrote this. I wish I had left a few more
> comments in the code for me to go on.
>
> Obviously the continue should be removed since it's not doing
> anything. I don't believe that we'd want a continue statement in
> there to get outer loop. That would change the current cmm_page_array
> pointer (pa_curr) to the next in the list after it may have just been
> reassigned to pa_last->next.
>
> It may be the case that an earlier version of the code had statements
> in the inner loop after that continue that I wanted to skip, or I just
> did something silly.
OK, thanks for looking at it. I came to a similar conclusion, but good to have
your review as well.
The CMM regression test suite will catch us if we get it wrong anyway.
cheers
prev parent reply other threads:[~2014-08-25 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 9:18 [PATCH] powerpc/pseries: Drop unnecessary continue Himangi Saraogi
2014-08-21 4:41 ` Michael Ellerman
2014-08-21 15:51 ` Robert Jennings
2014-08-25 4:16 ` Michael Ellerman [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=1408940178.7941.3.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=brking@linux.vnet.ibm.com \
--cc=himangi774@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=rcj4747@gmail.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).