From: Dominique Martinet <asmadeus@codewreck.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.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 Syrjälä" <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
Date: Tue, 19 Dec 2023 09:54:45 +0900 [thread overview]
Message-ID: <ZYDp1XeCrTlaOrIF@codewreck.org> (raw)
In-Reply-To: <CA+G9fYszCtMbbrurrjqpDzSa20ZX5mVdQ+RZv-KdiyLU4o5=0Q@mail.gmail.com>
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?
--
Dominique
next prev parent reply other threads:[~2023-12-19 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 13:51 [PATCH 5.10 00/62] 5.10.205-rc1 review Greg Kroah-Hartman
2023-12-18 15:24 ` Naresh Kamboju
2023-12-19 0:54 ` Dominique Martinet [this message]
2023-12-19 7:29 ` Greg Kroah-Hartman
2023-12-21 15:50 ` Shuah Khan
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=ZYDp1XeCrTlaOrIF@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=conor@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=maxime@cerno.tech \
--cc=naresh.kamboju@linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.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