From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755483AbdKNPos (ORCPT ); Tue, 14 Nov 2017 10:44:48 -0500 Received: from imap1.codethink.co.uk ([176.9.8.82]:47260 "EHLO imap1.codethink.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755448AbdKNPoi (ORCPT ); Tue, 14 Nov 2017 10:44:38 -0500 Message-ID: <1510674274.18523.31.camel@codethink.co.uk> Subject: Re: [PATCH 4.4 05/56] ARM: dts: imx53-qsb-common: fix FEC pinmux config From: Ben Hutchings To: Greg Kroah-Hartman , linux-kernel@vger.kernel.org Cc: stable@vger.kernel.org, Patrick Bruenn , Shawn Guo , Sasha Levin Date: Tue, 14 Nov 2017 15:44:34 +0000 In-Reply-To: <20171113125558.340246464@linuxfoundation.org> References: <20171113125557.613444087@linuxfoundation.org> <20171113125558.340246464@linuxfoundation.org> Organization: Codethink Ltd. Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2017-11-13 at 13:55 +0100, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > ------------------ > > From: Patrick Bruenn > > > [ Upstream commit 8b649e426336d7d4800ff9c82858328f4215ba01 ] > > The pinmux configuration in device tree was different from manual > muxing in /board/freescale/mx53loco/mx53loco.c > All pins were configured as NO_PAD_CTL(1 << 31), which was fine as the > bootloader already did the correct pinmuxing for us. > But recently u-boot is migrating to reuse device tree files from the > kernel tree, so it seems to be better to have the correct pinmuxing in > our files, too. [...] Presumably u-boot will reuse the *upstream* device tree files, which implies this doesn't need to be fixed on stable branches. Ben. -- Ben Hutchings Software Developer, Codethink Ltd.