From mboxrd@z Thu Jan 1 00:00:00 1970 From: LW@KARO-electronics.de (Lothar =?UTF-8?B?V2HDn21hbm4=?=) Date: Mon, 5 Feb 2018 16:03:19 +0100 Subject: [PATCH v2 BUGFIX] ARM: dts: imx6ull: fix the imx6ull-14x14-evk configuration In-Reply-To: <20180205103716.GY31354@dragon> References: <1516955159-21626-1-git-send-email-LW@KARO-electronics.de> <1516956738-24673-1-git-send-email-LW@KARO-electronics.de> <20180205075620.GO31354@dragon> <20180205105543.1711274c@karo-electronics.de> <20180205103716.GY31354@dragon> Message-ID: <20180205160319.297a74f8@karo-electronics.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi, On Mon, 5 Feb 2018 18:37:20 +0800 Shawn Guo wrote: > On Mon, Feb 05, 2018 at 10:55:43AM +0100, Lothar Wa?mann wrote: > > Hi, > > > > On Mon, 5 Feb 2018 15:56:22 +0800 Shawn Guo wrote: > > > 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 > > > > > > Which base is the patch generated against? I cannot apply it to any > > > branch in my tree. > > > > > The patch was generated against next-20180118 but also applies to > > next-20180205. > > It looks like you would really want this go into 4.16 as a fix? In that > case, I will need to wait for v4.16-rc1 to apply it. > I don't care much when and how it will be applied. I'm not using those files myself. Lothar Wa?mann From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lothar =?UTF-8?B?V2HDn21hbm4=?= Subject: Re: [PATCH v2 BUGFIX] ARM: dts: imx6ull: fix the imx6ull-14x14-evk configuration Date: Mon, 5 Feb 2018 16:03:19 +0100 Message-ID: <20180205160319.297a74f8@karo-electronics.de> References: <1516955159-21626-1-git-send-email-LW@KARO-electronics.de> <1516956738-24673-1-git-send-email-LW@KARO-electronics.de> <20180205075620.GO31354@dragon> <20180205105543.1711274c@karo-electronics.de> <20180205103716.GY31354@dragon> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: <20180205103716.GY31354@dragon> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Shawn Guo Cc: Mark Rutland , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Russell King , open list , Rob Herring , Sascha Hauer , Fabio Estevam , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" List-Id: devicetree@vger.kernel.org Hi, On Mon, 5 Feb 2018 18:37:20 +0800 Shawn Guo wrote: > On Mon, Feb 05, 2018 at 10:55:43AM +0100, Lothar Waßmann wrote: > > Hi, > > > > On Mon, 5 Feb 2018 15:56:22 +0800 Shawn Guo wrote: > > > 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 > > > > > > Which base is the patch generated against? I cannot apply it to any > > > branch in my tree. > > > > > The patch was generated against next-20180118 but also applies to > > next-20180205. > > It looks like you would really want this go into 4.16 as a fix? In that > case, I will need to wait for v4.16-rc1 to apply it. > I don't care much when and how it will be applied. I'm not using those files myself. Lothar Waßmann -- 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753027AbeBEPDb convert rfc822-to-8bit (ORCPT ); Mon, 5 Feb 2018 10:03:31 -0500 Received: from smtprelay03.ispgateway.de ([80.67.31.30]:20163 "EHLO smtprelay03.ispgateway.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753168AbeBEPDX (ORCPT ); Mon, 5 Feb 2018 10:03:23 -0500 Date: Mon, 5 Feb 2018 16:03:19 +0100 From: Lothar =?UTF-8?B?V2HDn21hbm4=?= To: Shawn Guo Cc: Mark Rutland , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Russell King , open list , Rob Herring , Sascha Hauer , Fabio Estevam , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Subject: Re: [PATCH v2 BUGFIX] ARM: dts: imx6ull: fix the imx6ull-14x14-evk configuration Message-ID: <20180205160319.297a74f8@karo-electronics.de> In-Reply-To: <20180205103716.GY31354@dragon> References: <1516955159-21626-1-git-send-email-LW@KARO-electronics.de> <1516956738-24673-1-git-send-email-LW@KARO-electronics.de> <20180205075620.GO31354@dragon> <20180205105543.1711274c@karo-electronics.de> <20180205103716.GY31354@dragon> Organization: Ka-Ro electronics GmbH MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-Df-Sender: bHdAa2Fyby1lbGVjdHJvbmljcy5kZQ== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, 5 Feb 2018 18:37:20 +0800 Shawn Guo wrote: > On Mon, Feb 05, 2018 at 10:55:43AM +0100, Lothar Waßmann wrote: > > Hi, > > > > On Mon, 5 Feb 2018 15:56:22 +0800 Shawn Guo wrote: > > > 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 > > > > > > Which base is the patch generated against? I cannot apply it to any > > > branch in my tree. > > > > > The patch was generated against next-20180118 but also applies to > > next-20180205. > > It looks like you would really want this go into 4.16 as a fix? In that > case, I will need to wait for v4.16-rc1 to apply it. > I don't care much when and how it will be applied. I'm not using those files myself. Lothar Waßmann