From: Shawn Guo <shawnguo@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/7] ARM: dts: imx6ul: add missing properties for sram
Date: Sun, 19 Jun 2022 16:55:34 +0800 [thread overview]
Message-ID: <20220619085534.GJ254723@dragon> (raw)
In-Reply-To: <20220613123357.441779-1-alexander.stein@ew.tq-group.com>
On Mon, Jun 13, 2022 at 02:33:51PM +0200, Alexander Stein wrote:
> All 3 properties are required by sram.yaml. Fixes the dtbs_check
> warning:
> sram@900000: '#address-cells' is a required property
> sram@900000: '#size-cells' is a required property
> sram@900000: 'ranges' is a required property
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
Applied all except #4, thanks!
_______________________________________________
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:[~2022-06-19 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 12:33 [PATCH 1/7] ARM: dts: imx6ul: add missing properties for sram Alexander Stein
2022-06-13 12:33 ` [PATCH 2/7] ARM: dts: imx6ul: change operating-points to uint32-matrix Alexander Stein
2022-06-13 12:33 ` [PATCH 3/7] ARM: dts: imx6ul: fix keypad compatible Alexander Stein
2022-06-13 12:33 ` [PATCH 4/7] ARM: dts: imx6ul: remove unsupported adc property Alexander Stein
2022-06-13 12:44 ` Baruch Siach
2022-06-13 13:01 ` (EXT) " Alexander Stein
2022-06-13 12:33 ` [PATCH 5/7] ARM: dts: imx6ul: fix csi node compatible Alexander Stein
2022-06-13 12:33 ` [PATCH 6/7] ARM: dts: imx6ul: fix lcdif " Alexander Stein
2022-06-13 12:33 ` [PATCH 7/7] ARM: dts: imx6ul: fix qspi " Alexander Stein
2022-06-19 8:55 ` 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=20220619085534.GJ254723@dragon \
--to=shawnguo@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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).