Re: [PATCH] arm64: dts: imx: Fix MU4_INT number

From: Fabio Estevam
Date: Wed Jan 16 2019 - 08:11:46 EST

Next message: Gao Xiang: "[PATCH v2 3/5] staging: erofs: move shrink accounting inside the function"
Previous message: Ramalingam C: "[PATCH v10 03/40] component: alloc component_match without any comp to match"
In reply to: Aisheng Dong: "RE: [PATCH] arm64: dts: imx: Fix MU4_INT number"
Next in thread: Daniel Baluta: "Re: [PATCH] arm64: dts: imx: Fix MU4_INT number"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Daniel,

On Tue, Jan 15, 2019 at 3:05 PM Daniel Baluta <daniel.baluta@xxxxxxx> wrote:
>
> MU4_INT correct number is 180, while 179 is for MU3_INT.
>
> Signed-off-by: Daniel Baluta <daniel.baluta@xxxxxxx>

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@xxxxxxxxx>

Next message: Gao Xiang: "[PATCH v2 3/5] staging: erofs: move shrink accounting inside the function"
Previous message: Ramalingam C: "[PATCH v10 03/40] component: alloc component_match without any comp to match"
In reply to: Aisheng Dong: "RE: [PATCH] arm64: dts: imx: Fix MU4_INT number"
Next in thread: Daniel Baluta: "Re: [PATCH] arm64: dts: imx: Fix MU4_INT number"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]