[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5AM5VRS7UiWuvAQ8vvTB8OM+iwofuYrbsL_yB9e0Z9Kyg@mail.gmail.com>
Date: Sun, 1 Jul 2018 22:05:10 -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
On Sun, Jul 1, 2018 at 10:03 PM, Anson Huang <anson.huang@....com> wrote:
> So that mean such kind of kernel patch will never be into kernel? Even if it is a
> necessary patch for fixing some other issues? I just wonder how this case being
> handled.
What is the issue that 5fe156f1cab4f fixes? It is not clear by looking
at the commit log.
Powered by blists - more mailing lists