From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Kukjin Kim <kgene@kernel.org>
Cc: devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] ARM: dts: Extend exynos5250-pinctrl nodes using labels instead of paths
Date: Wed, 8 Jul 2015 07:05:45 -0700 [thread overview]
Message-ID: <559D2E39.6060602@osg.samsung.com> (raw)
In-Reply-To: <559CDF66.6080609@samsung.com>
Hello Krzysztof,
On 07/08/2015 01:29 AM, Krzysztof Kozlowski wrote:
> On 08.07.2015 14:36, Javier Martinez Canillas wrote:
>> A previously defined Device Tree node, can be extended either by defining
>> a node using the same full path or by creating a label for the node and
>> referencing to it.
>>
>> Using full paths is more error prone since if there was a typo error, a
>> new node will be created instead of extending the node as it was desired.
>> This will lead to run-time errors that could be hard to detect.
>>
>> A misstyped label on the other hand, will cause a dtc compile error which
>
> s/misstyped/mistyped/
>
sigh, it's so ironic that I mistyped that.
Do you want me to re-post the whole series with the typo fixed or you /
Kukjin would fix in both patches when applying?
>> makes it easier to detect the mistake since happens at build-time instead.
>>
>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>> ---
>>
>> arch/arm/boot/dts/exynos5250-pinctrl.dtsi | 1600 ++++++++++++++---------------
>> 1 file changed, 799 insertions(+), 801 deletions(-)
>>
>
> I didn't look carefully enough to call it a review (I trust the 'diff'
> of yours) but it seems fine to me:
>
> Acked-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>
Thanks a lot for.
> Best regards,
> Krzysztof
>
Best regards,
--
Javier Martinez Canillas
Sr. Linux Kernel Developer
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2015-07-08 14:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 5:36 [PATCH 0/4] ARM: dts: Use labels instead of full paths for Exynos5 pinctrl nodes Javier Martinez Canillas
2015-07-08 5:36 ` [PATCH 1/4] ARM: dts: Include exynos5250-pinctrl after the nodes were defined Javier Martinez Canillas
2015-07-08 8:24 ` Krzysztof Kozlowski
2015-07-08 5:36 ` [PATCH 2/4] ARM: dts: Extend exynos5250-pinctrl nodes using labels instead of paths Javier Martinez Canillas
2015-07-08 8:29 ` Krzysztof Kozlowski
2015-07-08 14:05 ` Javier Martinez Canillas [this message]
2015-07-08 23:53 ` Krzysztof Kozlowski
2015-07-08 5:36 ` [PATCH 3/4] ARM: dts: Include exynos5420-pinctrl after the nodes were defined Javier Martinez Canillas
2015-07-08 8:25 ` Krzysztof Kozlowski
2015-07-08 8:27 ` [PATCH 0/4] ARM: dts: Use labels instead of full paths for Exynos5 pinctrl nodes Krzysztof Kozlowski
2015-07-08 14:15 ` Javier Martinez Canillas
2015-07-08 23:51 ` Krzysztof Kozlowski
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=559D2E39.6060602@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.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