From: Sudeep Holla <sudeep.holla@arm.com>
To: devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Subject: Re: [PATCH][RESEND] of: return of_get_cpu_node from of_cpu_device_node_get if CPUs are not registered
Date: Thu, 17 Aug 2017 16:49:11 +0100 [thread overview]
Message-ID: <11afa843-01c3-145e-8c0d-49c143b1f01d@arm.com> (raw)
In-Reply-To: <1502727520-5635-1-git-send-email-sudeep.holla@arm.com>
Hi Rob,
On 14/08/17 17:18, Sudeep Holla wrote:
> Instead of the callsites choosing between of_cpu_device_node_get if the
> CPUs are registered as of_node is populated by then and of_get_cpu_node
> when the CPUs are not yet registered as CPU of_nodes are not yet stashed
> thereby needing to parse the device tree, we can call of_get_cpu_node
> in case the CPUs are not yet registered in of_cpu_device_node_get.
>
> This will allow to use of_cpu_device_node_get anywhere hiding the
> details from the caller.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Frank Rowand <frowand.list@gmail.com>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> include/linux/of_device.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Hi Rob,
>
> You have already acked this patch, but I wanted you to pick up this via
> your tree and hence I am resending it. I tried pinging on that thread
> but I can understand that it's lost in your mailbox :)
>
Gentle ping!
--
Regards,
Sudeep
prev parent reply other threads:[~2017-08-17 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 16:18 Sudeep Holla
2017-08-17 15:49 ` Sudeep Holla [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=11afa843-01c3-145e-8c0d-49c143b1f01d@arm.com \
--to=sudeep.holla@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®