From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752709AbeBEKhv (ORCPT ); Mon, 5 Feb 2018 05:37:51 -0500 Received: from mail.kernel.org ([198.145.29.99]:59490 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752250AbeBEKhm (ORCPT ); Mon, 5 Feb 2018 05:37:42 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 80852217AA Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=shawnguo@kernel.org Date: Mon, 5 Feb 2018 18:37:20 +0800 From: Shawn Guo To: Lothar =?iso-8859-1?Q?Wa=DFmann?= 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: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180205105543.1711274c@karo-electronics.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Shawn