Received-SPF: pass (google.com: domain of linux-kernel+bounces-4810-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Tue, 19 Dec 2023 08:29:18 +0100
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>, stable@vger.kernel.org,
	patches@lists.linux.dev, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, pavel@denx.de, jonathanh@nvidia.com,
	f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
	srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
	allen.lkml@gmail.com, Maxime Ripard <maxime@cerno.tech>,
	Ville =?iso-8859-1?Q?Syrj=E4l=E4?= <ville.syrjala@linux.intel.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: [PATCH 5.10 00/62] 5.10.205-rc1 review
Message-ID: <2023121951-cement-repaying-f524@gregkh>
References: <20231218135046.178317233@linuxfoundation.org>
 <CA+G9fYszCtMbbrurrjqpDzSa20ZX5mVdQ+RZv-KdiyLU4o5=0Q@mail.gmail.com>
 <ZYDp1XeCrTlaOrIF@codewreck.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZYDp1XeCrTlaOrIF@codewreck.org>

On Tue, Dec 19, 2023 at 09:54:45AM +0900, Dominique Martinet wrote:
> Naresh Kamboju wrote on Mon, Dec 18, 2023 at 08:54:13PM +0530:
> > commit that is causing build failure,
> > drm/atomic: Pass the full state to CRTC atomic begin and flush
> > [ Upstream commit f6ebe9f9c9233a6114eb922aba9a0c9ccc2d2e14 ]
> 
> I also had to fix up a few nxp-provided drivers because of this commits,
> it seems a bit heavy-handed for stable trees when users can have a
> couple of out of tree modules.
> 
> It's marked as a stable dep of fe4c5f662097 ("drm/mediatek: Add spinlock
> for setting vblank event in atomic_begin") but that looks like it's only
> because of the context and it should be easy to backport that commit
> without the crtc atomic begin/flush rework -- what do you think?

Good catch, I've dropped those two larger dependent patches now and
fixed up the spinlock patch by hand to work properly.

I'll push out a -rc2 now, thanks!

greg k-h