From: Shawn Guo <shawnguo@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, stefan@agner.ch
Subject: Re: [PATCH] ARM: dts: vf: Fix memory node duplication
Date: Wed, 5 Dec 2018 15:54:03 +0800 [thread overview]
Message-ID: <20181205075401.GO3987@dragon> (raw)
In-Reply-To: <1543625092-24498-1-git-send-email-festevam@gmail.com>
On Fri, Nov 30, 2018 at 10:44:52PM -0200, Fabio Estevam wrote:
> Boards based on vf500/vf600 have duplicate memory nodes:
>
> - One coming from the board dts file: memory@
>
> - One coming from the vf500.dtsi/vf610m4.dtsi files.
>
> Fix the duplication by removing the memory node from the dtsi file
> and by adding 'device_type = "memory";' in the board dts.
>
> Reported-by: Rob Herring <robh@kernel.org>
Applied, thanks.
prev parent reply other threads:[~2018-12-05 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 0:44 [PATCH] ARM: dts: vf: Fix memory node duplication Fabio Estevam
2018-12-03 13:40 ` Stefan Agner
2018-12-05 7:54 ` Shawn Guo [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=20181205075401.GO3987@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=stefan@agner.ch \
/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).