From: Matthias Brugger <matthias.bgg@gmail.com>
To: Sam Shih <sam.shih@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: John Crispin <john@phrozen.org>, Ryder Lee <ryder.lee@kernel.org>
Subject: Re: [PATCH 1/2] arm64: dts: mediatek: update mt7986a memory node
Date: Tue, 1 Mar 2022 09:50:29 +0100 [thread overview]
Message-ID: <1940523d-4d98-b467-f518-7d5735e043e4@gmail.com> (raw)
In-Reply-To: <20220119123537.9968-2-sam.shih@mediatek.com>
On 19/01/2022 13:35, Sam Shih wrote:
> This patch updates the format of memory node in DT based on
> maintainer comments in the following thread:
> https://lore.kernel.org/all/bc0a9df0-8ba0-76ed-4522-43a3082f42b4@gmail.com/
>
> Signed-off-by: Sam Shih <sam.shih@mediatek.com>
Applied both with slightly better commit message. Please help the maintainer by
providing verbose commit message.
Regards,
Matthias
> ---
> arch/arm64/boot/dts/mediatek/mt7986a-rfb.dts | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt7986a-rfb.dts b/arch/arm64/boot/dts/mediatek/mt7986a-rfb.dts
> index 5cd760abff51..21e420829572 100644
> --- a/arch/arm64/boot/dts/mediatek/mt7986a-rfb.dts
> +++ b/arch/arm64/boot/dts/mediatek/mt7986a-rfb.dts
> @@ -19,7 +19,8 @@ chosen {
> stdout-path = "serial0:115200n8";
> };
>
> - memory {
> + memory@40000000 {
> + device_type = "memory";
> reg = <0 0x40000000 0 0x40000000>;
> };
> };
next prev parent reply other threads:[~2022-03-01 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 12:35 [PATCH 0/2] Update mt7986 memory node in DT Sam Shih
2022-01-19 12:35 ` [PATCH 1/2] arm64: dts: mediatek: update mt7986a memory node Sam Shih
2022-03-01 8:50 ` Matthias Brugger [this message]
2022-01-19 12:35 ` [PATCH 2/2] arm64: dts: mediatek: update mt7986b " Sam Shih
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=1940523d-4d98-b467-f518-7d5735e043e4@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=john@phrozen.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@kernel.org \
--cc=sam.shih@mediatek.com \
/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
all inboxes | Powered by JetHome®