From: Greg KH <gregkh@linuxfoundation.org>
To: Liu Ying <victor.liu@nxp.com>
Cc: Paul Pu <hui.pu@gehealthcare.com>,
p.zabel@pengutronix.de,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Lucas Stach <l.stach@pengutronix.de>,
HuanWang@gehealthcare.com, taowang@gehealthcare.com,
sebastian.reichel@collabora.com, ian.ray@gehealthcare.com,
stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/imx/ipuv3: ipuv3-plane: Round up plane width for IPUV3_CHANNEL_MEM_DC_SYNC
Date: Wed, 4 Sep 2024 11:13:43 +0200 [thread overview]
Message-ID: <2024090442-handrail-backwash-1493@gregkh> (raw)
In-Reply-To: <918336db-3c3e-4b5e-a9c8-096c9290f9d1@nxp.com>
On Wed, Sep 04, 2024 at 04:48:51PM +0800, Liu Ying wrote:
> On 09/04/2024, Paul Pu wrote:
> > Cc: stable@vger.kernel.org # 5.15+
>
> Why 5.15+ ?
Because the commit referenced in Fixes: was backported there.
If you want to be picky, just drop the "# 5.15+" and our tools will rely
on the Fixes: tag and everyone will be happy.
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-04 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 2:43 [PATCH] drm: imx: ipuv3-plane: fix HDMI cannot work for odd screen resolutions Paul Pu
2024-09-04 5:40 ` Liu Ying
2024-09-04 7:44 ` Pu, Hui
2024-09-04 6:21 ` Greg KH
2024-09-04 7:47 ` Pu, Hui
2024-09-04 7:54 ` [PATCH v2] drm/imx/ipuv3: ipuv3-plane: Round up plane width for IPUV3_CHANNEL_MEM_DC_SYNC Paul Pu
2024-09-04 8:31 ` Philipp Zabel
2024-09-04 8:48 ` Liu Ying
2024-09-04 9:07 ` Pu, Hui
2024-09-04 9:13 ` Greg KH [this message]
2024-09-04 9:27 ` Liu Ying
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=2024090442-handrail-backwash-1493@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=HuanWang@gehealthcare.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=hui.pu@gehealthcare.com \
--cc=ian.ray@gehealthcare.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.reichel@collabora.com \
--cc=shawnguo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=taowang@gehealthcare.com \
--cc=tzimmermann@suse.de \
--cc=victor.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox