[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5D_kakB82dEcXrU4EZARLj90US8Zf+sGgaKkZvUG3t=PA@mail.gmail.com>
Date: Wed, 16 Jan 2019 11:12:12 -0200
From: Fabio Estevam <festevam@...il.com>
To: Daniel Baluta <daniel.baluta@....com>
Cc: "shawnguo@...nel.org" <shawnguo@...nel.org>,
"mark.rutland@....com" <mark.rutland@....com>,
Aisheng Dong <aisheng.dong@....com>,
Anson Huang <anson.huang@....com>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
Fabio Estevam <fabio.estevam@....com>,
"S.j. Wang" <shengjiu.wang@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm64: dts: imx: Fix MU4_INT number
Hi Daniel,
On Tue, Jan 15, 2019 at 3:05 PM Daniel Baluta <daniel.baluta@....com> wrote:
>
> MU4_INT correct number is 180, while 179 is for MU3_INT.
>
> Signed-off-by: Daniel Baluta <daniel.baluta@....com>
Two nitpicks:
1. In the Subject it would be better to specify the SoC name:
arm64: dts: imx8qxp: Fix MU4_INT number
2. It would be nice to add a Fixes tag
Reviewed-by: Fabio Estevam <festevam@...il.com>
Powered by blists - more mailing lists