linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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@canonical.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/5] Support for TQMa6ULx & TQMa6ULxL modules
Date: Tue, 22 Feb 2022 10:34:23 +0800	[thread overview]
Message-ID: <20220222023423.GX2249@dragon> (raw)
In-Reply-To: <20220222022833.GW2249@dragon>

On Tue, Feb 22, 2022 at 10:28:39AM +0800, Shawn Guo wrote:
> On Mon, Feb 21, 2022 at 05:04:14PM +0100, Alexander Stein wrote:
> > Alexander Stein (4):
> >   ARM: dts: imx6ul: add TQ-Systems MBa6ULx device trees
> >   ARM: dts: imx6ul: add TQ-Systems MBa6ULxL device trees
> >   ARM: dts: imx6ull: add TQ-Systems MBa6ULLx device trees
> >   ARM: dts: imx6ull: add TQ-Systems MBa6ULLxL device trees
> > 
> > Matthias Schiffer (1):
> >   dt-bindings: arm: fsl: add TQ Systems boards based on i.MX6UL(L)
> 
> Applied all, thanks!

I replied too soon.

../arch/arm/boot/dts/mba6ulx.dtsi:46.10-50.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:52.10-56.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:58.10-63.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:52.10-56.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:58.10-63.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:58.10-63.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
ERROR: Input tree has errors, aborting (use -f to force output)
make[2]: *** [../scripts/Makefile.lib:351: arch/arm/boot/dts/imx6ul-tqma6ul2-mba6ulx.dtb] Error 2
make[2]: *** Waiting for unfinished jobs....
  DTC     arch/arm/boot/dts/imx6ul-pico-dwarf.dtb
../arch/arm/boot/dts/mba6ulx.dtsi:46.10-50.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:52.10-56.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:58.10-63.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:52.10-56.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:58.10-63.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:58.10-63.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
ERROR: Input tree has errors, aborting (use -f to force output)
make[2]: *** [../scripts/Makefile.lib:351: arch/arm/boot/dts/imx6ul-tqma6ul1-mba6ulx.dtb] Error 2
../arch/arm/boot/dts/mba6ulx.dtsi:46.10-50.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:52.10-56.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:58.10-63.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:52.10-56.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:58.10-63.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
../arch/arm/boot/dts/mba6ulx.dtsi:58.10-63.5: ERROR (duplicate_node_names): /gpio-keys/button: Duplicate node name
ERROR: Input tree has errors, aborting (use -f to force output)
make[2]: *** [../scripts/Makefile.lib:351: arch/arm/boot/dts/imx6ul-tqma6ul2l-mba6ulx.dtb] Error 2
make[1]: *** [/home/r65073/repos/korg/imx/Makefile:1370: dtbs] Error 2
make[1]: Leaving directory '/home/r65073/repos/korg/imx/IMX6'
make: *** [Makefile:219: __sub-make] Error 2

Shawn

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-02-22  2:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 16:04 [PATCH v2 0/5] Support for TQMa6ULx & TQMa6ULxL modules Alexander Stein
2022-02-21 16:04 ` [PATCH v2 1/5] dt-bindings: arm: fsl: add TQ Systems boards based on i.MX6UL(L) Alexander Stein
2022-02-21 17:21   ` Krzysztof Kozlowski
2022-02-21 16:04 ` [PATCH v2 2/5] ARM: dts: imx6ul: add TQ-Systems MBa6ULx device trees Alexander Stein
2022-02-21 16:04 ` [PATCH v2 3/5] ARM: dts: imx6ul: add TQ-Systems MBa6ULxL " Alexander Stein
2022-02-21 16:04 ` [PATCH v2 4/5] ARM: dts: imx6ull: add TQ-Systems MBa6ULLx " Alexander Stein
2022-02-21 16:04 ` [PATCH v2 5/5] ARM: dts: imx6ull: add TQ-Systems MBa6ULLxL " Alexander Stein
2022-02-22  2:28 ` [PATCH v2 0/5] Support for TQMa6ULx & TQMa6ULxL modules Shawn Guo
2022-02-22  2:34   ` Shawn Guo [this message]
2022-02-22  7:01     ` (EXT) " Alexander Stein

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=20220222023423.GX2249@dragon \
    --to=shawnguo@kernel.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --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).