From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64: topology: Add support for topology DT bindings
Date: Wed, 19 Mar 2014 16:50:58 +0000 [thread overview]
Message-ID: <20140319165058.GA21513@red-moon> (raw)
In-Reply-To: <20140319163339.GP11706@sirena.org.uk>
On Wed, Mar 19, 2014 at 04:33:39PM +0000, Mark Brown wrote:
> On Wed, Mar 19, 2014 at 04:04:14PM +0000, Lorenzo Pieralisi wrote:
> > > +void __init init_cpu_topology(void)
> > > +{
> > > + int ret;
> > > +
> > > + reset_cpu_topology();
> > > +
> > > + ret = parse_dt_topology();
> > > + if (ret != 0)
> > > + reset_cpu_topology();
>
> > ret is unused so should be removed. You could remove the first reset call and
>
> I'm sorry, I don't follow? The use is quoted above...
if (parse_dt_topology())
reset_cpu_topology();
If you want to leave ret there I do not care, I flag what I notice.
> > use static initialization for that, it is a matter of taste though.
>
> Static initialisation can't cover the calls to set_power_scale() and
> having a different thing for default and unwinding cases seems likely to
> be error prone.
>
> > A comment is in order, whatever approach you go for.
>
> I'm not sure what the confusion is here so I don't know what a comment
> would clarify. Could you say what it is you find confusing please?
It is worth explaining why you want to reset the topology for the sake
of completeness, I do not think I am asking too much.
parse_cluster() return value issue I flagged up must be fixed though.
Thanks,
Lorenzo
next prev parent reply other threads:[~2014-03-19 16:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 8:59 [PATCH 1/3] arm64: topology: Add support for topology DT bindings Mark Brown
2014-03-05 8:59 ` [PATCH 2/3] arm64: topology: Tell the scheduler about the relative power of cores Mark Brown
2014-03-05 8:59 ` [PATCH 3/3] arm64: topology: Provide relative power numbers for cores Mark Brown
2014-03-19 16:04 ` [PATCH 1/3] arm64: topology: Add support for topology DT bindings Lorenzo Pieralisi
2014-03-19 16:33 ` Mark Brown
2014-03-19 16:50 ` Lorenzo Pieralisi [this message]
2014-03-19 17:03 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2014-03-19 18:02 Mark Brown
2014-03-20 11:26 ` Lorenzo Pieralisi
2014-03-20 13:43 ` Mark Brown
2014-03-20 17:19 ` Catalin Marinas
2014-03-20 17:52 ` Mark Brown
2014-03-21 14:52 ` Catalin Marinas
2014-03-21 11:13 ` Mark Brown
2014-03-21 15:01 ` Catalin Marinas
2014-03-21 15:36 ` Mark Brown
2014-03-20 18:08 ` Lorenzo Pieralisi
2014-03-21 11:32 ` Mark Brown
2014-03-21 15:16 ` Lorenzo Pieralisi
2014-03-21 16:06 ` Mark Brown
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=20140319165058.GA21513@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).