[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5D8v4KM9S4ooHTDbA+vc8BZN_eO_wDuOPA+8Hcq-SmLDw@mail.gmail.com>
Date: Sun, 1 Jul 2018 22:00:21 -0300
From: Fabio Estevam <festevam@...il.com>
To: Anson Huang <anson.huang@....com>
Cc: Shawn Guo <shawnguo@...nel.org>, Robin Gong <yibin.gong@....com>,
Mark Rutland <mark.rutland@....com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
dl-linux-imx <linux-imx@....com>,
Sascha Hauer <kernel@...gutronix.de>,
Fabio Estevam <fabio.estevam@....com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on
Hi Anson,
On Sun, Jul 1, 2018 at 9:57 PM, Anson Huang <anson.huang@....com> wrote:
> Just want to know how to handle such case? The kernel patch will never
> be applied or is there any way to make kernel patch and dtb patch applied
> together to avoid any breakage?
We always want to avoid breaking a working dtb when it is used with a
newer kernel.
In this case we need to revert the kernel patch as it causes
regression with old dtbs.
Powered by blists - more mailing lists