linux-kernel - Re: [PATCH 4.4 05/56] ARM: dts: imx53-qsb-common: fix FEC pinmux config

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1510674274.18523.31.camel@codethink.co.uk>
Date:   Tue, 14 Nov 2017 15:44:34 +0000
From:   Ben Hutchings <ben.hutchings@...ethink.co.uk>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Cc:     stable@...r.kernel.org, Patrick Bruenn <p.bruenn@...khoff.com>,
        Shawn Guo <shawnguo@...nel.org>,
        Sasha Levin <alexander.levin@...izon.com>
Subject: Re: [PATCH 4.4 05/56] ARM: dts: imx53-qsb-common: fix FEC pinmux
 config

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 <p.bruenn@...khoff.com>
> 
> 
> [ Upstream commit 8b649e426336d7d4800ff9c82858328f4215ba01 ]
> 
> The pinmux configuration in device tree was different from manual
> muxing in <u-boot>/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.