[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <918336db-3c3e-4b5e-a9c8-096c9290f9d1@nxp.com>
Date: Wed, 4 Sep 2024 16:48:51 +0800
From: Liu Ying <victor.liu@....com>
To: Paul Pu <hui.pu@...ealthcare.com>, p.zabel@...gutronix.de,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
Shawn Guo <shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>, Lucas Stach <l.stach@...gutronix.de>
Cc: HuanWang@...ealthcare.com, taowang@...ealthcare.com,
sebastian.reichel@...labora.com, ian.ray@...ealthcare.com,
stable@...r.kernel.org, dri-devel@...ts.freedesktop.org,
imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] drm/imx/ipuv3: ipuv3-plane: Round up plane width for
IPUV3_CHANNEL_MEM_DC_SYNC
On 09/04/2024, Paul Pu wrote:
> Cc: stable@...r.kernel.org # 5.15+
Why 5.15+ ?
I think it should be 6.3+ because below commit introduced in v6.3
moves ipuv3-plane.c from one directory to another, which makes
this patch not being applicable to v6.2.
commit 4b6cb2b67da8 ("drm/imx: move IPUv3 driver into separate subdirectory")
Or, it could be 6.2+ because the culprit commit 4333472f8d7b was
introduced in v6.2.
--
Regards,
Liu Ying
Powered by blists - more mailing lists