From: Laura Abbott <lauraa@codeaurora.org>
To: Tushar Behera <trblinux@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Kevin Hilman <khilman@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robherring2@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linaro-kernel@lists.linaro.org, afaerber@suse.de,
devicetree@vger.kernel.org
Subject: Re: [PATCHv2 1/3] of: Split early_init_dt_scan into two parts
Date: Mon, 07 Jul 2014 17:54:22 -0700 [thread overview]
Message-ID: <53BB413E.40900@codeaurora.org> (raw)
In-Reply-To: <1404266608-3274-1-git-send-email-lauraa@codeaurora.org>
On 7/1/2014 7:03 PM, Laura Abbott wrote:
> Currently, early_init_dt_scan validates the header, sets the
> boot params, and scans for chosen/memory all in one function.
> Split this up into two separate functions (validation/setting
> boot params in one, scanning in another) to allow for
> additional setup between boot params and scanning the memory.
>
> Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
I haven't heard anything more on this series but the holiday weekend
in the US probably affected that.
Grant/Rob are you okay with taking this through the devicetree tree
if this gets a few more acks or would you rather this go through
an ARM tree?
Thanks,
Laura
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
prev parent reply other threads:[~2014-07-08 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 2:03 [PATCHv2 1/3] of: Split early_init_dt_scan into two parts Laura Abbott
2014-07-02 2:03 ` [PATCHv2 2/3] of: Add memory limiting function for flattened devicetrees Laura Abbott
2014-07-02 2:03 ` [PATCHv2 3/3] arm: Add devicetree fixup machine function Laura Abbott
2014-07-02 6:00 ` [PATCHv2 1/3] of: Split early_init_dt_scan into two parts Tushar Behera
2014-07-08 0:54 ` Laura Abbott [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=53BB413E.40900@codeaurora.org \
--to=lauraa@codeaurora.org \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=khilman@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robherring2@gmail.com \
--cc=trblinux@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).