From: Grant Likely <grant.likely@secretlab.ca>
To: Grant Likely <grant.likely@secretlab.ca>,
linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org
Subject: Re: [resend] Make the kernel accept ePAPR style phandle information
Date: Mon, 1 Feb 2010 14:20:32 -0700 [thread overview]
Message-ID: <fa686aa41002011320p4b2bd7b9r53b58892cbe1ff6@mail.gmail.com> (raw)
In-Reply-To: <20100201045242.GB8095@yookeroo>
On Sun, Jan 31, 2010 at 9:52 PM, David Gibson
<david@gibson.dropbear.id.au> wrote:
> Grant, I've updated this for your current test-devicetree branch.
> Please apply.
>
> Currently when processing flattened device trees, the kernel expects
> the phandle in a property called "linux,phandle". The ePAPR spec -
> not being Linux specific - instead requires phandles to be encoded in
> a property named simply "phandle". This patch makes the kernel accept
> either form when unflattening the device tree.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Applied, thanks.
g.
prev parent reply other threads:[~2010-02-01 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 4:52 [resend] Make the kernel accept ePAPR style phandle information David Gibson
2010-02-01 10:00 ` Wolfram Sang
2010-02-01 21:20 ` Grant Likely [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=fa686aa41002011320p4b2bd7b9r53b58892cbe1ff6@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=devicetree-discuss@ozlabs.org \
--cc=linuxppc-dev@ozlabs.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