[PATCH 0/5][-next] TTM bo reservation and fencing improvements

[Sedat Dilek]

Against which GIT tree is this patchset, against latest drm-next GIT they fail?
Missing a patch or patchset?

- Sedat -

$ cd /mnt/sdb5/linux-kernel/drm-2.6

$ git branch
* drm-next
  master

$ git describe
v2.6.34-rc5-32040-g01d5a1f

$ cat patches/series
drm-ttm-next/1-5-drm-ttm-Optimize-ttm_eu_backoff_reservation.patch
drm-ttm-next/2-5-drm-ttm-Don-t-deadlock-on-recursive-multi-bo-reservations.patch
drm-ttm-next/3-5-drm-ttm-radeon-nouveau-Kill-the-bo-lock-in-favour-of-a-bo-device-fence_lock.patch
drm-ttm-next/4-5-drm-ttm-Improved-fencing-of-buffer-object-lists.patch
drm-ttm-next/5-5-drm-ttm-vmwgfx-Have-TTM-manage-the-validation-sequence..patch
drm-ttm-next/1-1-drm-radeon-Use-the-ttm-execbuf-utilities.patch

$ quilt -f push
Wende Patch drm-ttm-next/1-5-drm-ttm-Optimize-ttm_eu_backoff_reservation.patch
an
patching file drivers/gpu/drm/ttm/ttm_execbuf_util.c
Hunk #1 succeeded at 35 (offset -64 lines).

Jetzt in Patch drm-ttm-next/1-5-drm-ttm-Optimize-ttm_eu_backoff_reservation.patch
$ quilt -f push
Wende Patch drm-ttm-next/2-5-drm-ttm-Don-t-deadlock-on-recursive-multi-bo-reservations.patch
an
patching file drivers/gpu/drm/ttm/ttm_bo.c
Hunk #1 FAILED at 223.
1 out of 1 hunk FAILED -- saving rejects to file
drivers/gpu/drm/ttm/ttm_bo.c.rej
patching file include/drm/ttm/ttm_bo_driver.h
Hunk #2 FAILED at 871.
1 out of 2 hunks FAILED -- saving rejects to file
include/drm/ttm/ttm_bo_driver.h.rej
Patch drm-ttm-next/2-5-drm-ttm-Don-t-deadlock-on-recursive-multi-bo-reservations.patch
angewandt (erzwungen, muss aktualisiert werden (Refresh))