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: Fri, 21 Mar 2014 15:16:17 +0000 [thread overview]
Message-ID: <20140321151617.GA11938@red-moon> (raw)
In-Reply-To: <20140321113202.GJ11706@sirena.org.uk>
On Fri, Mar 21, 2014 at 11:32:02AM +0000, Mark Brown wrote:
> On Thu, Mar 20, 2014 at 06:08:36PM +0000, Lorenzo Pieralisi wrote:
>
> > > > This ifdef can be removed, CONFIG_OF is always selected for arm64 and
> > > > the !CONFIG_OF path
>
> > > This has been present since the very first time these patches were
> > > posted but hasn't been mentioned as being a problem previously.
>
> > I am sorry, I missed it, doing my best to help you get it through.
>
> Please try to consider this from a submitter point of view; it is quite
> frustrating every time something that has been around for a while and
> fairly obvious gets identified as a new issue, it makes it hard to have
> confidence that addressing review comments is moving closer to getting
> things accepted.
I understand that and I apologize, but I will still flag issues up
as long as I find some. For instance, I noticed patch is missing
of_node_put() calls almost everywhere DT nodes are parsed and we have
to fix that before merging it. I can do that to save another respin.
[...]
> > I know, it is complex, there is little we can do about that and it is
> > code run just at cold boot and freed later so I deem that acceptable.
>
> It's not that anything is really complex (the requirements keep on
> evolving but nothing is particularly hard), it's that we could most
> likely have had something useful for people already.
I agree and you are right.
In order to add all these checks this code is getting ways too complex for
my taste, it is not your problem and it is not mine either, I just can't help
notice though.
Patch is complete and I think it is almost ready to get merged.
Instead of bothering you with another respin with minor changes I suggest
I will pick the last version up, diff what's needed and repost it here for
final look so that we are done with it.
Please let me know if that's plausible, thank you.
Lorenzo
next prev parent reply other threads:[~2014-03-21 15:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 18:02 [PATCH 1/3] arm64: topology: Add support for topology DT bindings Mark Brown
2014-03-19 18:02 ` [PATCH 2/3] arm64: topology: Tell the scheduler about the relative power of cores Mark Brown
2014-03-19 18:02 ` [PATCH 3/3] arm64: topology: Provide relative power numbers for cores Mark Brown
2014-03-20 11:26 ` [PATCH 1/3] arm64: topology: Add support for topology DT bindings 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 [this message]
2014-03-21 16:06 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2014-03-05 8:59 Mark Brown
2014-03-19 16:04 ` Lorenzo Pieralisi
2014-03-19 16:33 ` Mark Brown
2014-03-19 16:50 ` Lorenzo Pieralisi
2014-03-19 17:03 ` 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=20140321151617.GA11938@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).