[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <11058ce79d91a49e47be47bd369ddc111875fa23.camel@nxp.com>
Date: Wed, 16 Jan 2019 13:24:49 +0000
From: Daniel Baluta <daniel.baluta@....com>
To: "festevam@...il.com" <festevam@...il.com>
CC: dl-linux-imx <linux-imx@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Aisheng Dong <aisheng.dong@....com>,
Fabio Estevam <fabio.estevam@....com>,
"mark.rutland@....com" <mark.rutland@....com>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Anson Huang <anson.huang@....com>,
"S.j. Wang" <shengjiu.wang@....com>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>
Subject: Re: [PATCH] arm64: dts: imx: Fix MU4_INT number
On Wed, 2019-01-16 at 11:12 -0200, Fabio Estevam wrote:
> 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>
Thanks Fabio for review. Fixed in v2.
Powered by blists - more mailing lists