From: Matthew McClintock <msm@freescale.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Kumar Gala <kumar.gala@freescale.com>,
linuxppc-dev@lists.ozlabs.org, Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH V4] powerpc/prom: Export device tree physical address via proc
Date: Wed, 14 Jul 2010 10:42:43 -0500 [thread overview]
Message-ID: <1279122163.13098.2.camel@localhost> (raw)
In-Reply-To: <C26140FB-4F77-4D8E-B6C4-63BC9C9EDD83@kernel.crashing.org>
On Wed, 2010-07-14 at 17:35 +0200, Segher Boessenkool wrote:
> > V4: Fixed misspelling
>
> Any particular reason you fixed only one of the two
> mispelings I pointed out? (device tree is two words,
> not one).
Ahh, my fault.
>
> > + prop = of_find_property(node, "linux,devicetree-start", NULL);
> > + if (prop)
> > + prom_remove_property(node, prop);
> > +
> > + prop = of_find_property(node, "linux,devicetree-end", NULL);
> > + if (prop)
> > + prom_remove_property(node, prop);
> > +
> > + flat_dt_start = virt_to_phys(initial_boot_params);
> > + flat_dt_end = virt_to_phys(initial_boot_params)
> > + + initial_boot_params->totalsize;
> > + prom_add_property(node, &flat_dt_start_prop);
> > + prom_add_property(node, &flat_dt_end_prop);
>
> You could use one property instead of two; use addr+len
> like every other property does.
>
> You also should use a better name for the property; is this
> the previous kernel's device tree? Just "device-tree" makes
> no sense, it is not pointing to "the" device tree for sure!
>
What about just one node called "flat-device-tree"?
-Matthew
next prev parent reply other threads:[~2010-07-14 15:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 15:18 [PATCH V4] powerpc/prom: Export device tree physical address via proc Matthew McClintock
2010-07-14 15:33 ` Tabi Timur-B04825
2010-07-14 15:35 ` Segher Boessenkool
2010-07-14 15:42 ` Matthew McClintock [this message]
2010-07-14 15:46 ` Segher Boessenkool
2010-07-15 6:17 ` Matthew McClintock
2010-07-15 6:21 ` Grant Likely
2010-07-15 15:19 ` Matthew McClintock
2010-07-15 16:22 ` Grant Likely
2010-07-15 16:39 ` Matthew McClintock
2010-07-15 16:57 ` Grant Likely
2010-07-15 18:03 ` Matthew McClintock
2010-07-15 18:37 ` Grant Likely
2010-07-15 18:58 ` Matthew McClintock
2010-07-15 19:18 ` Grant Likely
2010-07-16 5:44 ` Mitch Bradley
2010-07-17 16:41 ` Segher Boessenkool
2010-07-19 4:24 ` Matthew McClintock
2010-07-30 1:38 ` David Gibson
2010-07-30 1:23 ` David Gibson
2010-07-19 0:09 ` Benjamin Herrenschmidt
2010-07-19 4:34 ` Matthew McClintock
2010-07-18 23:41 ` Benjamin Herrenschmidt
2010-07-19 4:28 ` Matthew McClintock
2010-07-19 4:32 ` Grant Likely
2010-07-19 16:57 ` Scott Wood
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=1279122163.13098.2.camel@localhost \
--to=msm@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=segher@kernel.crashing.org \
--cc=timur@freescale.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).