public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@redhat.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>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"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-misc-fixes
Date: Thu, 23 Apr 2026 07:41:50 +0200	[thread overview]
Message-ID: <20260423-realistic-eager-reindeer-4dacf7@houat> (raw)

[-- Attachment #1: Type: text/plain, Size: 4288 bytes --]

Hi Sima, Dave,

Here's this week drm-misc-fixes PR.

Please not that the last commit (2fc87d37be1b) has a missing link and
creates a dim warning.

Maxime

drm-misc-fixes-2026-04-23:
This week in drm-misc-fixes, we have:
- A patch to raise the vblank timeout to avoid it on virtual drivers
- a state check fix for stm_lvds
- a use-after-free fix for dma-buf
- a mapping fix for panthor
- a device_node reference leak fix for arcgpu
- a bridge reference leak fix for dw-mipi-dsi
- a sparse warning fix for dma-fence
- a kconfig fix for hv
- a memory leak fix for nouveau
- a fix to duplicate colorop when duplicating states
- a panel initialisation order fix for visionox-rm69299
- a fix to prevent an infinite loop for v3d
- an overflow fix for nouveau
The following changes since commit 857fa8f2a5b184c206c703a3d9ce05cea683cfed:

  accel: ethosu: Add hardware dependency hint (2026-04-02 15:18:14 -0500)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/misc/kernel.git tags/drm-misc-fixes-2026-04-23

for you to fetch changes up to 2fc87d37be1b730a149b035f9375fdb8cc5333a5:

  drm/nouveau: fix u32 overflow in pushbuf reloc bounds check (2026-04-20 21:23:14 +0200)

----------------------------------------------------------------
This week in drm-misc-fixes, we have:
- A patch to raise the vblank timeout to avoid it on virtual drivers
- a state check fix for stm_lvds
- a use-after-free fix for dma-buf
- a mapping fix for panthor
- a device_node reference leak fix for arcgpu
- a bridge reference leak fix for dw-mipi-dsi
- a sparse warning fix for dma-fence
- a kconfig fix for hv
- a memory leak fix for nouveau
- a fix to duplicate colorop when duplicating states
- a panel initialisation order fix for visionox-rm69299
- a fix to prevent an infinite loop for v3d
- an overflow fix for nouveau

----------------------------------------------------------------
Adrián Larumbe (2):
      drm/panthor: Extend VM locked region for remap case to be a superset
      drm/panthor: Fix outdated function documentation

Andi Shyti (1):
      dma-buf: fix UAF in dma_buf_put() tracepoint

Ashutosh Desai (1):
      drm/v3d: Reject empty multisync extension to prevent infinite loop

David Carlier (1):
      drm/nouveau: fix nvkm_device leak on aperture removal failure

Greg Kroah-Hartman (1):
      drm/nouveau: fix u32 overflow in pushbuf reloc bounds check

Guido Günther (1):
      drm/panel: visionox-rm69299: Make use of prepare_prev_first

Luca Ceresoli (1):
      drm/arcpgu: fix device node leak

Marek Vasut (1):
      drm/bridge: stm_lvds: Do not fail atomic_check on disabled connector

Melissa Wen (1):
      drm/drm_atomic: duplicate colorop states if plane color pipeline in use

Osama Abdelkader (1):
      drm/bridge: dw-mipi-dsi: Fix bridge leak when host attach fails

Thomas Zimmermann (2):
      drm/atomic: Increase timeout in drm_atomic_helper_wait_for_vblanks()
      hv: Select CONFIG_SYSFB only for CONFIG_HYPERV_VMBUS

Tvrtko Ursulin (1):
      dma-fence: Silence sparse warning in dma_fence_describe

Yongbang Shi (1):
      MAINTAINERS: split hisilicon maintenance and add Yongbang Shi for hibmc-drm matainers

 MAINTAINERS                                    | 13 ++++++++++---
 drivers/dma-buf/dma-buf.c                      |  3 +--
 drivers/dma-buf/dma-fence.c                    |  4 ++--
 drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c  |  6 +++++-
 drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi2.c |  6 +++++-
 drivers/gpu/drm/drm_atomic_helper.c            | 14 +++++++++++++-
 drivers/gpu/drm/nouveau/nouveau_drm.c          |  2 +-
 drivers/gpu/drm/nouveau/nouveau_gem.c          |  2 +-
 drivers/gpu/drm/panel/panel-visionox-rm69299.c |  2 ++
 drivers/gpu/drm/panthor/panthor_gem.c          |  2 +-
 drivers/gpu/drm/panthor/panthor_mmu.c          | 19 +++++++++++++++++++
 drivers/gpu/drm/stm/lvds.c                     |  6 +++---
 drivers/gpu/drm/tiny/arcpgu.c                  |  3 ++-
 drivers/gpu/drm/v3d/v3d_submit.c               |  5 +++++
 drivers/hv/Kconfig                             |  2 +-
 include/drm/drm_atomic.h                       |  3 ++-
 16 files changed, 73 insertions(+), 19 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]

             reply	other threads:[~2026-04-23  5:41 UTC|newest]

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  5:41 Maxime Ripard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-09  8:15 [PULL] drm-misc-fixes Maxime Ripard
2026-04-02  7:52 Maxime Ripard
2026-03-26  7:17 Maxime Ripard
2026-03-19  7:20 Maxime Ripard
2026-03-12  7:30 Maxime Ripard
2026-03-06  6:41 Maxime Ripard
2026-03-05  8:09 Maxime Ripard
2026-02-26  8:36 Maxime Ripard
2026-02-05  9:53 Maarten Lankhorst
2026-01-29 17:01 Maarten Lankhorst
2026-01-22  9:50 Maarten Lankhorst
2026-01-16 11:46 Maarten Lankhorst
2026-01-07  9:45 Maarten Lankhorst
2025-12-30 19:40 Maarten Lankhorst
2025-12-18 10:05 Maarten Lankhorst
2025-12-10 11:29 Maarten Lankhorst
2025-11-27  8:10 Thomas Zimmermann
2025-11-20 15:13 Thomas Zimmermann
2025-11-13 13:23 Thomas Zimmermann
2025-11-06 13:12 Thomas Zimmermann
2025-10-30 19:56 Thomas Zimmermann
2025-10-31 18:10 ` Simona Vetter
2025-10-23  8:34 Thomas Zimmermann
2025-10-24 11:36 ` Simona Vetter
2025-10-16 14:16 Thomas Zimmermann
2025-10-09 12:00 Thomas Zimmermann
2025-09-25 11:32 Maxime Ripard
2025-09-18  8:24 Maxime Ripard
2025-09-11 16:04 Maxime Ripard
2025-09-03  7:57 Maxime Ripard
2025-08-28  6:32 Maxime Ripard
2025-08-21  8:12 Maxime Ripard
2025-07-23  9:18 Maarten Lankhorst
2025-07-16  7:42 Maarten Lankhorst
2025-07-10  8:59 Maarten Lankhorst
2025-07-11 12:15 ` Simona Vetter
2025-07-03 15:26 Maarten Lankhorst
2025-06-27  7:04 Maarten Lankhorst
2025-06-19  8:12 Maarten Lankhorst
2025-06-12 11:53 Maarten Lankhorst
2025-06-06  7:28 Thomas Zimmermann
2025-06-06 13:03 ` Simona Vetter
2025-05-28 15:35 Thomas Zimmermann
2025-06-06 12:38 ` Simona Vetter
2025-05-22 11:49 Thomas Zimmermann
2025-05-15 12:55 Thomas Zimmermann
2025-05-08 10:49 Thomas Zimmermann
2025-04-30  8:24 Maxime Ripard
2025-04-22 15:12 Thomas Zimmermann
2025-04-17  8:40 Thomas Zimmermann
2025-04-10 12:24 Thomas Zimmermann
2025-03-20  8:38 Maxime Ripard
2025-03-13  7:36 Maxime Ripard
2025-03-06 10:32 Maxime Ripard
2025-02-27 14:10 Maxime Ripard
2025-02-20  8:30 Maxime Ripard
2025-02-13 15:30 Maxime Ripard
2025-02-06  9:15 Maxime Ripard
2025-01-24  8:29 Thomas Zimmermann
2025-01-24 10:42 ` Simona Vetter
2025-01-15  9:22 Maarten Lankhorst
2025-01-02  8:47 Maarten Lankhorst
2024-12-19 18:10 Maarten Lankhorst
2024-12-05 19:48 Maarten Lankhorst
2024-11-28 13:59 Thomas Zimmermann
2024-11-21 13:18 Thomas Zimmermann
2024-11-14 14:22 Thomas Zimmermann
2024-11-08  8:50 Thomas Zimmermann
2024-10-31 14:43 Thomas Zimmermann
2024-10-24 12:49 Thomas Zimmermann
2024-10-17 11:55 Thomas Zimmermann
2024-10-10 13:37 Thomas Zimmermann
2024-10-02 15:15 Thomas Zimmermann
2024-09-26 12:10 Thomas Zimmermann
2024-09-12  8:49 Maxime Ripard
2024-09-05 14:19 Maxime Ripard
2024-08-29 14:51 Maxime Ripard
2024-08-22 12:39 Thomas Zimmermann
2024-08-15 13:17 Thomas Zimmermann
2024-08-08  7:48 Maxime Ripard
2024-08-01  9:00 Maxime Ripard
2024-07-11  9:51 Maarten Lankhorst
2024-07-04 12:27 Maarten Lankhorst
2024-07-04 14:49 ` Daniel Vetter
2024-06-26 15:35 Maarten Lankhorst
2024-06-14  8:13 Maarten Lankhorst
2024-06-06 22:09 Maarten Lankhorst
2024-05-30 19:23 Thomas Zimmermann
2024-05-23 18:47 Thomas Zimmermann
2024-05-16  7:26 Thomas Zimmermann
2024-05-10  7:20 Thomas Zimmermann
2024-05-02 19:21 Thomas Zimmermann
2024-04-25 10:24 Thomas Zimmermann
2024-04-18  7:22 Thomas Zimmermann
2024-04-11  7:34 Thomas Zimmermann
2024-04-04 10:48 Thomas Zimmermann
2024-03-28 13:44 Thomas Zimmermann
2024-03-07  8:44 Maxime Ripard
2024-02-29 13:37 Maxime Ripard
2024-02-29 13:54 ` Matthew Auld
2024-03-06 14:26   ` Maxime Ripard

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=20260423-realistic-eager-reindeer-4dacf7@houat \
    --to=mripard@redhat.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=matthew.brost@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