From: Fabio Estevam <festevam@gmail.com>
To: Anson Huang <anson.huang@nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>, Robin Gong <yibin.gong@nxp.com>,
Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on
Date: Sun, 1 Jul 2018 22:00:21 -0300 [thread overview]
Message-ID: <CAOMZO5D8v4KM9S4ooHTDbA+vc8BZN_eO_wDuOPA+8Hcq-SmLDw@mail.gmail.com> (raw)
In-Reply-To: <AM3PR04MB1315E7AED2BCE2265E6C443DF5430@AM3PR04MB1315.eurprd04.prod.outlook.com>
Hi Anson,
On Sun, Jul 1, 2018 at 9:57 PM, Anson Huang <anson.huang@nxp.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.
WARNING: multiple messages have this Message-ID (diff)
From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on
Date: Sun, 1 Jul 2018 22:00:21 -0300 [thread overview]
Message-ID: <CAOMZO5D8v4KM9S4ooHTDbA+vc8BZN_eO_wDuOPA+8Hcq-SmLDw@mail.gmail.com> (raw)
In-Reply-To: <AM3PR04MB1315E7AED2BCE2265E6C443DF5430@AM3PR04MB1315.eurprd04.prod.outlook.com>
Hi Anson,
On Sun, Jul 1, 2018 at 9:57 PM, Anson Huang <anson.huang@nxp.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.
next prev parent reply other threads:[~2018-07-02 1:00 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 12:34 [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on Robin Gong
2018-06-25 12:34 ` Robin Gong
2018-06-25 5:53 ` Anson Huang
2018-06-25 5:53 ` Anson Huang
2018-06-25 5:53 ` Anson Huang
2018-07-01 9:34 ` Shawn Guo
2018-07-01 9:34 ` Shawn Guo
2018-07-01 23:32 ` Fabio Estevam
2018-07-01 23:32 ` Fabio Estevam
2018-07-01 23:32 ` Fabio Estevam
2018-07-02 0:53 ` Anson Huang
2018-07-02 0:53 ` Anson Huang
2018-07-02 0:53 ` Anson Huang
2018-07-02 0:54 ` Fabio Estevam
2018-07-02 0:54 ` Fabio Estevam
2018-07-02 0:54 ` Fabio Estevam
2018-07-02 0:57 ` Anson Huang
2018-07-02 0:57 ` Anson Huang
2018-07-02 0:57 ` Anson Huang
2018-07-02 1:00 ` Fabio Estevam [this message]
2018-07-02 1:00 ` Fabio Estevam
2018-07-02 1:00 ` Fabio Estevam
2018-07-02 1:03 ` Anson Huang
2018-07-02 1:03 ` Anson Huang
2018-07-02 1:03 ` Anson Huang
2018-07-02 1:05 ` Fabio Estevam
2018-07-02 1:05 ` Fabio Estevam
2018-07-02 1:05 ` Fabio Estevam
2018-07-02 1:09 ` Anson Huang
2018-07-02 1:09 ` Anson Huang
2018-07-02 1:09 ` Anson Huang
2018-07-02 1:17 ` Fabio Estevam
2018-07-02 1:17 ` Fabio Estevam
2018-07-02 1:17 ` Fabio Estevam
2018-07-02 1:19 ` Anson Huang
2018-07-02 1:19 ` Anson Huang
2018-07-02 1:19 ` Anson Huang
2018-07-02 2:12 ` Robin Gong
2018-07-02 2:12 ` Robin Gong
2018-07-02 2:12 ` Robin Gong
2018-07-02 23:14 ` Fabio Estevam
2018-07-02 23:14 ` Fabio Estevam
2018-07-02 23:14 ` Fabio Estevam
2018-07-03 5:38 ` Shawn Guo
2018-07-03 5:38 ` Shawn Guo
2018-07-03 5:38 ` Shawn Guo
2018-07-03 7:44 ` Anson Huang
2018-07-03 7:44 ` Anson Huang
2018-07-03 7:44 ` Anson Huang
2018-07-03 11:10 ` Fabio Estevam
2018-07-03 11:10 ` Fabio Estevam
2018-07-03 11:10 ` Fabio Estevam
2018-07-04 1:42 ` Robin Gong
2018-07-04 1:42 ` Robin Gong
2018-07-04 1:42 ` Robin Gong
2018-07-04 6:56 ` Lothar Waßmann
2018-07-04 6:56 ` Lothar Waßmann
2018-07-04 6:56 ` Lothar Waßmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOMZO5D8v4KM9S4ooHTDbA+vc8BZN_eO_wDuOPA+8Hcq-SmLDw@mail.gmail.com \
--to=festevam@gmail.com \
--cc=anson.huang@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=yibin.gong@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.