Received: by 10.223.164.202 with SMTP id h10csp682079wrb; Tue, 14 Nov 2017 08:00:42 -0800 (PST) X-Google-Smtp-Source: AGs4zMZu+ew/78w6LLwXLOGnesHogtIUK8k6cjJYWZJab6i+KGAwMW5uCi+KBZT8iPRqM3xoehQV X-Received: by 10.98.11.155 with SMTP id 27mr14139672pfl.242.1510675242521; Tue, 14 Nov 2017 08:00:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510675242; cv=none; d=google.com; s=arc-20160816; b=KXIe6zPWwwpAH3EZojEWlXda7jrcOD5O1LqhEhflxapPMPUkG30wZlWzIOnD5rvjjF zO7azaB523xzBXCwtkBApGQ9WeE1yUDRHeAu6prlWq2cJsWAAn4hkfYYHYnQitI/wj0T xfv5OXSH7XJUoKTiXxmZXoNL6ZTaqIG9v6TjaIbLGR8r0iEeF/GWX1+LHTlb4p/KM4x+ uvUl1JT6p8q4YwzYBVcYN1dXf4GareedVk9Xi6vQ+t/9+qLT4QEKmhiYOO+jPue2IkIw jhxheqLxJlHzJhVsg7qT5heX7ceNug0B2GU+341WqsDcBnZQVaa/Hwis4DHncz3yh3pO aF1Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:date:cc:to:from:subject :message-id:arc-authentication-results; bh=Q2Cpuldq7q9anqpjPJSIDkitmoOm+0nBBF8IzWuaeJY=; b=v2u0ykwcwL+XF7QTc9EuCxnDNzQSE65XCGsRcOfXyU6+f/C/ckDU/DQcfmzgWDB8kY TzCsj3FMf3GJmMryxM9IX6s2R7v29qFUrIEsn3tXLe5bRbfJ3kqYLwdmV2HntmmYwSeM X8FulcjuOY/vvDLzv6lWMlGB0Y0FIfZo5JmDPR6+5ujrFS3CJfK4gIOjQ1bCH0INx8Sz B9QaBEU7MXfgTjVaRIpFQGYAG7eaGaeoUIUWuFTUWcgCTroV0MQ2PONsZxt88aWGlaUo kDGocTccaBzIDyCh4WVj1jivch9pDRCzWmdJGqniOanuH54NPFQqx8vcWfOHZ74q2Evt cU4A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=codethink.co.uk Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p8si16351259pls.804.2017.11.14.08.00.29; Tue, 14 Nov 2017 08:00:42 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=codethink.co.uk Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755480AbdKNPor (ORCPT + 88 others); Tue, 14 Nov 2017 10:44:47 -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 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126] helo=xylophone) by imap1.codethink.co.uk with esmtpsa (Exim 4.84_2 #1 (Debian)) id 1eEdO8-0003Rx-HU; Tue, 14 Nov 2017 15:44:36 +0000 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 Precedence: bulk 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. From 1583958277683898726@xxx Mon Nov 13 13:38:47 +0000 2017 X-GM-THRID: 1583955652239079861 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread