From: Jani Nikula <jani.nikula@intel.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dim-tools@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PULL] drm-intel-fixes follow-up
Date: Fri, 01 Dec 2023 10:40:42 +0200 [thread overview]
Message-ID: <87fs0m48ol.fsf@intel.com> (raw)
Hi Dave & Sima -
As Ville observed in [1], yesterday's fixes pull depends on a commit
that wasn't included, and VRR might suffer without it. Here's the
missing one.
I see that Dave already sent the drm fixes pull on to Linus, but here
goes nothing.
BR,
Jani.
[1] https://lore.kernel.org/r/ZWjlapi4-QmzxwYO@intel.com
drm-intel-fixes-2023-12-01-1:
drm/i915 fixes for v6.7-rc4 #2:
- d21a3962d304 ("drm/i915: Call intel_pre_plane_updates() also for pipes
getting enabled") in the previous fixes pull depends on a change that
wasn't included. Pick it up.
The following changes since commit d21a3962d3042e6f56ad324cf18bdd64a1e6ecfa:
drm/i915: Call intel_pre_plane_updates() also for pipes getting enabled (2023-11-29 10:23:25 +0200)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-fixes-2023-12-01-1
for you to fetch changes up to 96d7e79401364c6e9a63af5f74f76792b03cb832:
drm/i915: Check pipe active state in {planes,vrr}_{enabling,disabling}() (2023-12-01 10:19:11 +0200)
----------------------------------------------------------------
drm/i915 fixes for v6.7-rc4 #2:
- d21a3962d304 ("drm/i915: Call intel_pre_plane_updates() also for pipes
getting enabled") in the previous fixes pull depends on a change that
wasn't included. Pick it up.
----------------------------------------------------------------
Ville Syrjälä (1):
drm/i915: Check pipe active state in {planes,vrr}_{enabling,disabling}()
drivers/gpu/drm/i915/display/intel_display.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
--
Jani Nikula, Intel
reply other threads:[~2023-12-01 8:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87fs0m48ol.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mripard@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tzimmermann@suse.de \
/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