[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025060258-properly-pristine-f112@gregkh>
Date: Mon, 2 Jun 2025 07:31:19 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Sasha Levin <sashal@...nel.org>
Cc: patches@...ts.linux.dev, stable@...r.kernel.org,
Jonas Karlman <jonas@...boo.se>,
Nicolas Dufresne <nicolas.dufresne@...labora.com>,
Christopher Obbard <chris.obbard@...labora.com>,
Hans Verkuil <hverkuil@...all.nl>, ezequiel@...guardiasur.com.ar,
mchehab@...nel.org, matthias.bgg@...il.com,
angelogioacchino.delregno@...labora.com,
linux-media@...r.kernel.org, linux-rockchip@...ts.infradead.org,
linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH AUTOSEL 6.15 052/110] media: rkvdec: h264: Use
bytesperline and buffer height as virstride
On Sun, Jun 01, 2025 at 07:23:34PM -0400, Sasha Levin wrote:
> From: Jonas Karlman <jonas@...boo.se>
>
> [ Upstream commit d5e0aa61470c48ddc04d433a00e79cef8716377a ]
>
> Use bytesperline and buffer height to calculate the strides configured.
>
> This does not really change anything other than ensuring the
> bytesperline that is signaled to userspace matches what is configured
> in HW.
>
> Signed-off-by: Jonas Karlman <jonas@...boo.se>
> Reviewed-by: Nicolas Dufresne <nicolas.dufresne@...labora.com>
> Tested-by: Nicolas Dufresne <nicolas.dufresne@...labora.com>
> Tested-by: Christopher Obbard <chris.obbard@...labora.com>
> Signed-off-by: Nicolas Dufresne <nicolas.dufresne@...labora.com>
> Signed-off-by: Hans Verkuil <hverkuil@...all.nl>
> Signed-off-by: Sasha Levin <sashal@...nel.org>
> ---
>
> ### Key Reasons for NO Backport: 1. **Not a Bug Fix**: The commit
> message explicitly states "This does not really change anything other
> than ensuring the bytesperline that is signaled to userspace matches
> what is configured in HW." This is not fixing a functional bug but
> rather improving consistency between userspace and hardware
> configuration.
As the bot said "NO", why was this picked up?
thanks,
greg k-h
Powered by blists - more mailing lists