From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>, Matthew Daley <mattjd@gmail.com>
Cc: Julien Grall <julien.grall@citrix.com>, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen/arm: correct duplicate MPIDR check to actually skip the node
Date: Mon, 11 Nov 2013 19:54:18 +0000 [thread overview]
Message-ID: <528135EA.8060603@linaro.org> (raw)
In-Reply-To: <1384186202.19117.71.camel@kazak.uk.xensource.com>
On 11/11/2013 04:10 PM, Ian Campbell wrote:
> On Fri, 2013-11-08 at 13:32 +1300, Matthew Daley wrote:
>> Signed-off-by: Matthew Daley <mattjd@gmail.com>
>> ---
>> I assume this was what was really intended...
>
Indeed, that for spotting this error !
> CCing Julien... But yes it looks like it.
>
>> xen/arch/arm/smpboot.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/xen/arch/arm/smpboot.c b/xen/arch/arm/smpboot.c
>> index b836be4..6c90fa6 100644
>> --- a/xen/arch/arm/smpboot.c
>> +++ b/xen/arch/arm/smpboot.c
>> @@ -161,9 +161,11 @@ void __init smp_init_cpus(void)
>> printk(XENLOG_WARNING
>> "cpu node `%s`: duplicate /cpu reg properties in the DT\n",
>> dt_node_full_name(cpu));
>> - continue;
>> + break;
>> }
>> }
>> + if ( j != cpuidx )
>> + continue;
>
> Took me a moment to figure out what this was for. I'm half minded to
> suggest this is one of those places where a "goto next_cpu" would have
> been ok, I'd definitely want a second opinion on that though!
>
I'm happy with the both solutions:
Acked-by: Julien Grall <julien.grall@linaro.org>
--
Julien Grall
next prev parent reply other threads:[~2013-11-11 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 0:32 [PATCH] xen/arm: correct duplicate MPIDR check to actually skip the node Matthew Daley
2013-11-11 16:10 ` Ian Campbell
2013-11-11 19:54 ` Julien Grall [this message]
2013-11-19 14:53 ` Ian Campbell
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=528135EA.8060603@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=mattjd@gmail.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).