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>,
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 for v6.19-rc1
Date: Fri, 12 Dec 2025 10:02:26 +0200 [thread overview]
Message-ID: <281309f78560bcceebac8d5c0511efe66baf641c@intel.com> (raw)
Hi Dave & Sima -
drm-intel-next-fixes-2025-12-12:
drm/i915 fixes for v6.19-rc1:
- Fix format string truncation warning
- FIx runtime PM reference during fbdev BO creation
BR,
Jani.
The following changes since commit c7685d11108acb387e44e3d81194d0d8959eaa44:
Merge tag 'topic/drm-intel-plane-color-pipeline-2025-12-04' of https://gitlab.freedesktop.org/drm/i915/kernel into drm-next (2025-12-05 10:27:57 +1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/i915/kernel.git tags/drm-intel-next-fixes-2025-12-12
for you to fetch changes up to 1c7f9e528f8f488b060b786bfb90b40540854db3:
drm/i915: Fix format string truncation warning (2025-12-09 15:53:12 +0200)
----------------------------------------------------------------
drm/i915 fixes for v6.19-rc1:
- Fix format string truncation warning
- FIx runtime PM reference during fbdev BO creation
----------------------------------------------------------------
Ard Biesheuvel (1):
drm/i915: Fix format string truncation warning
Dibin Moolakadan Subrahmanian (1):
drm/i915/fbdev: Hold runtime PM ref during fbdev BO creation
drivers/gpu/drm/i915/display/intel_fbdev.c | 11 +++++++----
drivers/gpu/drm/i915/intel_memory_region.h | 2 +-
2 files changed, 8 insertions(+), 5 deletions(-)
--
Jani Nikula, Intel
reply other threads:[~2025-12-12 8:02 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=281309f78560bcceebac8d5c0511efe66baf641c@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=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).