From: Jani Nikula <jani.nikula@intel.com>
To: Dave Airlie <airlied@gmail.com>, Simona Vetter <simona.vetter@ffwll.ch>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: [PULL] drm-intel-next-fixes
Date: Tue, 25 Mar 2025 11:07:34 +0200 [thread overview]
Message-ID: <878qota36x.fsf@intel.com> (raw)
Hi Dave & Sima -
drm-intel-next-fixes-2025-03-25:
drm/i915 fixes for v6.15 merge window:
- Bounds check for scalers in DSC prefill latency computation
- Fix build by adding a missing include
BR,
Jani.
The following changes since commit 5da39dce1fa3c81dc6552a16a9f748ba2980d630:
Merge tag 'drm-xe-next-fixes-2025-03-12' of https://gitlab.freedesktop.org/drm/xe/kernel into drm-next (2025-03-14 17:02:11 +1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/i915/kernel.git tags/drm-intel-next-fixes-2025-03-25
for you to fetch changes up to af9ec6e4682c089028d763b0b77c04fa2ddae268:
drm/i915/display: Fix build error without DRM_FBDEV_EMULATION (2025-03-20 18:27:21 +0200)
----------------------------------------------------------------
drm/i915 fixes for v6.15 merge window:
- Bounds check for scalers in DSC prefill latency computation
- Fix build by adding a missing include
----------------------------------------------------------------
Ankit Nautiyal (1):
drm/i915/watermark: Check bounds for scaler_users for dsc prefill latency
Yue Haibing (1):
drm/i915/display: Fix build error without DRM_FBDEV_EMULATION
drivers/gpu/drm/i915/display/intel_fbdev.h | 2 ++
drivers/gpu/drm/i915/display/skl_watermark.c | 5 ++++-
2 files changed, 6 insertions(+), 1 deletion(-)
--
Jani Nikula, Intel
next reply other threads:[~2025-03-25 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 9:07 Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-05 7:48 [PULL] drm-intel-next-fixes Jani Nikula
2025-06-05 8:35 Joonas Lahtinen
2025-05-28 6:56 Joonas Lahtinen
2025-05-22 6:59 Joonas Lahtinen
2025-05-15 8:27 Joonas Lahtinen
2024-11-21 8:37 Tvrtko Ursulin
2024-09-26 7:45 Joonas Lahtinen
2024-09-19 9:49 Joonas Lahtinen
2024-09-12 8:59 Joonas Lahtinen
2024-07-25 7:44 Tvrtko Ursulin
2024-07-18 9:30 Tvrtko Ursulin
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=878qota36x.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--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;
as well as URLs for NNTP newsgroup(s).