From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 BUGFIX] ARM: dts: imx6ull: fix the imx6ull-14x14-evk configuration
Date: Mon, 5 Feb 2018 15:56:22 +0800 [thread overview]
Message-ID: <20180205075620.GO31354@dragon> (raw)
In-Reply-To: <1516956738-24673-1-git-send-email-LW@KARO-electronics.de>
On Fri, Jan 26, 2018 at 09:52:18AM +0100, Lothar Wa?mann wrote:
> imx6ull-14x14-evk.dts currently includes the imx6ul.dtsi file for an
> i.MX6ULL SoC which is plain wrong.
>
> Rename the current imx6ul-14x14-evk.dts to .dtsi and include it from
> imx6ul-14x14-evk.dts and imx6ull-14x14-evk.dts, so that both can
> include the appropriate SoC specific (imx6ul.dtsi/imx6ull.dtsi) file.
>
> Signed-off-by: Lothar Wa?mann <LW@KARO-electronics.de>
Which base is the patch generated against? I cannot apply it to any
branch in my tree.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: "Lothar Waßmann" <LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
Cc: Sascha Hauer <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Fabio Estevam <fabio.estevam-3arQi8VN3Tc@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
open list <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 BUGFIX] ARM: dts: imx6ull: fix the imx6ull-14x14-evk configuration
Date: Mon, 5 Feb 2018 15:56:22 +0800 [thread overview]
Message-ID: <20180205075620.GO31354@dragon> (raw)
In-Reply-To: <1516956738-24673-1-git-send-email-LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
On Fri, Jan 26, 2018 at 09:52:18AM +0100, Lothar Waßmann wrote:
> imx6ull-14x14-evk.dts currently includes the imx6ul.dtsi file for an
> i.MX6ULL SoC which is plain wrong.
>
> Rename the current imx6ul-14x14-evk.dts to .dtsi and include it from
> imx6ul-14x14-evk.dts and imx6ull-14x14-evk.dts, so that both can
> include the appropriate SoC specific (imx6ul.dtsi/imx6ull.dtsi) file.
>
> Signed-off-by: Lothar Waßmann <LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
Which base is the patch generated against? I cannot apply it to any
branch in my tree.
Shawn
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: "Lothar Waßmann" <LW@KARO-electronics.de>
Cc: Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 BUGFIX] ARM: dts: imx6ull: fix the imx6ull-14x14-evk configuration
Date: Mon, 5 Feb 2018 15:56:22 +0800 [thread overview]
Message-ID: <20180205075620.GO31354@dragon> (raw)
In-Reply-To: <1516956738-24673-1-git-send-email-LW@KARO-electronics.de>
On Fri, Jan 26, 2018 at 09:52:18AM +0100, Lothar Waßmann wrote:
> imx6ull-14x14-evk.dts currently includes the imx6ul.dtsi file for an
> i.MX6ULL SoC which is plain wrong.
>
> Rename the current imx6ul-14x14-evk.dts to .dtsi and include it from
> imx6ul-14x14-evk.dts and imx6ull-14x14-evk.dts, so that both can
> include the appropriate SoC specific (imx6ul.dtsi/imx6ull.dtsi) file.
>
> Signed-off-by: Lothar Waßmann <LW@KARO-electronics.de>
Which base is the patch generated against? I cannot apply it to any
branch in my tree.
Shawn
next prev parent reply other threads:[~2018-02-05 7:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 8:25 [PATCH BUGFIX] ARM: dts: imx6ull: fix the imx6ull-14x14-evk configuration Lothar Waßmann
2018-01-26 8:25 ` Lothar Waßmann
2018-01-26 8:25 ` Lothar Waßmann
2018-01-26 8:52 ` [PATCH v2 " Lothar Waßmann
2018-01-26 8:52 ` Lothar Waßmann
2018-01-26 8:52 ` Lothar Waßmann
2018-02-05 7:56 ` Shawn Guo [this message]
2018-02-05 7:56 ` Shawn Guo
2018-02-05 7:56 ` Shawn Guo
2018-02-05 9:55 ` Lothar Waßmann
2018-02-05 9:55 ` Lothar Waßmann
2018-02-05 9:55 ` Lothar Waßmann
2018-02-05 10:37 ` Shawn Guo
2018-02-05 10:37 ` Shawn Guo
2018-02-05 10:37 ` Shawn Guo
2018-02-05 15:03 ` Lothar Waßmann
2018-02-05 15:03 ` Lothar Waßmann
2018-02-05 15:03 ` Lothar Waßmann
2018-02-08 7:09 ` Shawn Guo
2018-02-08 7:09 ` Shawn Guo
2018-02-08 7:09 ` Shawn Guo
2018-01-26 8:54 ` [PATCH " Dong Aisheng
2018-01-26 8:54 ` Dong Aisheng
2018-01-26 20:00 ` kbuild test robot
2018-01-26 20:00 ` kbuild test robot
2018-01-26 20:00 ` kbuild test robot
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=20180205075620.GO31354@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.