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
Subject: Re: [PATCH 1/2] ARM: dts: imx23: Fix memory node duplicaton
Date: Wed, 28 Nov 2018 16:52:54 +0800 [thread overview]
Message-ID: <20181128085252.GO20643@dragon> (raw)
In-Reply-To: <1543234136-6824-1-git-send-email-festevam@gmail.com>
On Mon, Nov 26, 2018 at 10:08:55AM -0200, Fabio Estevam wrote:
> Boards based on imx23 have duplicate memory nodes:
>
> - One coming from the board dts file: memory@
>
> - One coming from the imx23.dtsi file.
>
> 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>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2018-11-28 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 12:08 [PATCH 1/2] ARM: dts: imx23: Fix memory node duplicaton Fabio Estevam
2018-11-26 12:08 ` [PATCH 2/2] ARM: dts: imx28: " Fabio Estevam
2018-11-28 8:52 ` 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=20181128085252.GO20643@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 \
/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).