From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>, Stephen Boyd <stephen.boyd@linaro.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] of: remove *phandle properties from expanded device tree
Date: Tue, 18 Apr 2017 14:08:26 -0700 [thread overview]
Message-ID: <58F6804A.3080206@gmail.com> (raw)
In-Reply-To: <58F19A75.80500@gmail.com>
Hi Rob,
Please do not apply this patch series.
The more context I look at, the less this approach seems good.
I hope to have a simpler version completed quickly.
Thanks,
- Frank
On 04/14/17 20:58, Frank Rowand wrote:
> Hi Stephen,
>
> I left you off the distribution list, sorry...
>
> On 04/14/17 20:55, frowand.list@gmail.com wrote:
>> From: Frank Rowand <frank.rowand@sony.com>
>>
>> Remove "phandle" and "linux,phandle" properties from the internal
>> device tree. The phandle will still be in the struct device_node
>> phandle field.
>>
>> This is to resolve the issue found by Stephen Boyd [1] when he changed
>> the type of struct property.value from void * to const void *. As
>> a result of the type change, the overlay code had compile errors
>> where the resolver updates phandle values.
>>
>> [1] http://lkml.iu.edu/hypermail/linux/kernel/1702.1/04160.html
>>
>> Patch 1 is the phandle related changes.
>>
>> Patches 2 - 4 are minor fixups for issues that became visible
>> while implementing patch 1.
>>
>> Frank Rowand (4):
>> of: remove *phandle properties from expanded device tree
>> of: make __of_attach_node() static
>> of: be consistent in form of file mode
>> of: detect invalid phandle in overlay
>>
>> drivers/of/base.c | 53 +++++++++++++++++++++++++++++++++++++++++++++----
>> drivers/of/dynamic.c | 31 ++++++++++++++++-------------
>> drivers/of/fdt.c | 40 ++++++++++++++++++++++---------------
>> drivers/of/of_private.h | 1 -
>> drivers/of/overlay.c | 8 +++++---
>> drivers/of/resolver.c | 23 +--------------------
>> include/linux/of.h | 1 +
>> 7 files changed, 97 insertions(+), 60 deletions(-)
next prev parent reply other threads:[~2017-04-18 21:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 3:55 [PATCH 0/4] of: remove *phandle properties from expanded device tree frowand.list
2017-04-15 3:55 ` [PATCH 1/4] " frowand.list
2017-04-15 3:59 ` Frank Rowand
2017-04-15 3:55 ` [PATCH 2/4] of: make __of_attach_node() static frowand.list
2017-04-15 3:59 ` Frank Rowand
2017-04-15 3:55 ` [PATCH 3/4] of: be consistent in form of file mode frowand.list
2017-04-15 3:59 ` Frank Rowand
2017-04-15 3:55 ` [PATCH 4/4] of: detect invalid phandle in overlay frowand.list
2017-04-15 3:59 ` Frank Rowand
2017-04-15 3:58 ` [PATCH 0/4] of: remove *phandle properties from expanded device tree Frank Rowand
2017-04-18 21:08 ` Frank Rowand [this message]
2017-04-19 13:38 ` Rob Herring
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=58F6804A.3080206@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stephen.boyd@linaro.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