From: Florian Fainelli <f.fainelli@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org
Cc: "Mark Rutland" <mark.rutland@arm.com>,
robh@kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, "Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"open list" <linux-kernel@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"maintainer:BROADCOM BCM5301X ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH] ARM: dts: bcm: Add missing device_type = "memory" property
Date: Mon, 20 May 2019 09:30:29 -0700 [thread overview]
Message-ID: <d28229cf-3fc5-9599-f886-9e2a0da28080@gmail.com> (raw)
In-Reply-To: <20190509171527.2331-1-f.fainelli@gmail.com>
On 5/9/19 10:15 AM, Florian Fainelli wrote:
> During the removal of the skeleton.dtsi file with commit abe60a3a7afb
> ("ARM: dts: Kill off skeleton{64}.dtsi") a number of Broadcom SoCs were
> converted, but a few were left unoticed, now causing boot failures with
> v5.1 since the kernel cannot find suitable memory.
>
> Updating the .dtsi files with the property will be done next, since
> there are some memory nodes that do not follow the proper naming
> convention and lack an unit name.
>
> Fixes: abe60a3a7afb ("ARM: dts: Kill off skeleton{64}.dtsi")
> Reported-by: Kevin Hilman <khilman@kernel.org>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Applied to devicetree/fixes, thanks!
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-05-20 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 17:15 [PATCH] ARM: dts: bcm: Add missing device_type = "memory" property Florian Fainelli
2019-05-20 16:30 ` Florian Fainelli [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=d28229cf-3fc5-9599-f886-9e2a0da28080@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=zajec5@gmail.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;
as well as URLs for NNTP newsgroup(s).