Danilo Krummrich b715dcd3db drm/nouveau: uapi: don't pass NO_PREFETCH flag implicitly ... Currently, NO_PREFETCH is passed implicitly through drm_nouveau_gem_pushbuf_push::length and drm_nouveau_exec_push::va_len. Since this is a direct representation of how the HW is programmed it isn't really future proof for a uAPI. Hence, fix this up for the new uAPI and split up the va_len field of struct drm_nouveau_exec_push, such that we keep 32bit for va_len and 32bit for flags. For drm_nouveau_gem_pushbuf_push::length at least provide NOUVEAU_GEM_PUSHBUF_NO_PREFETCH to indicate the bit shift. While at it, fix up nv50_dma_push() as well, such that the caller doesn't need to encode the NO_PREFETCH flag into the length parameter. Signed-off-by: Danilo Krummrich <dakr@redhat.com> Reviewed-by: Faith Ekstrand <faith.ekstrand@collabora.com> Link: https://patchwork.freedesktop.org/patch/msgid/20230823181746.3446-1-dakr@redhat.com		2023-08-24 01:43:00 +02:00
..
asm-generic	asm-generic updates for 6.5	2023-07-06 10:06:04 -07:00
drm	drm/nouveau: uapi: don't pass NO_PREFETCH flag implicitly	2023-08-24 01:43:00 +02:00
linux	hardening fixes for v6.5-rc1	2023-07-08 12:08:39 -07:00
misc
mtd
rdma	RDMA/bnxt_re: Enable low latency push	2023-06-21 14:13:17 -03:00
scsi	scsi: ufs: core: Add support for qTimestamp attribute	2023-07-05 21:44:07 -04:00
sound	Merge branch 'for-next' into for-linus	2023-06-26 15:23:23 +02:00
video
xen
Kbuild