From: Jani Nikula <jani.nikula@intel.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
dim-tools@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Sean Paul <sean@poorly.run>,
intel-gfx@lists.freedesktop.org
Subject: [PULL] drm-intel-next-fixes for v5.17-rc1
Date: Wed, 29 Dec 2021 13:44:01 +0200 [thread overview]
Message-ID: <87ee5vk54u.fsf@intel.com> (raw)
Hi Dave & Daniel -
A lone FBC fix for drm-next for the merge window.
BR,
Jani.
The following changes since commit 040bf2a9446f6ba267225d34dc4a9b14d11e5092:
Merge tag 'drm-misc-next-fixes-2021-12-23' of git://anongit.freedesktop.org/drm/drm-misc into drm-next (2021-12-24 06:24:06 +1000)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2021-12-29
for you to fetch changes up to c65fe9cbbfd61dbc12868f9ed4940c80fcb249e8:
drm/i915/fbc: Remember to update FBC state even when not reallocating CFB (2021-12-27 11:46:48 +0200)
----------------------------------------------------------------
drm/i915 fixes for the v5.17-rc1:
- Update FBC state even when not reallocating CFB
----------------------------------------------------------------
Ville Syrjälä (1):
drm/i915/fbc: Remember to update FBC state even when not reallocating CFB
drivers/gpu/drm/i915/display/intel_fbc.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
Jani Nikula, Intel Open Source Graphics Center
reply other threads:[~2021-12-29 11:44 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=87ee5vk54u.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=rodrigo.vivi@intel.com \
--cc=sean@poorly.run \
--cc=tvrtko.ursulin@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