drm/ttm: fix documentation of ttm_bo_reserve
authorNicolai Hähnle <Nicolai.Haehnle@amd.com>
Sat, 12 Dec 2015 16:42:23 +0000 (11:42 -0500)
committerDave Airlie <airlied@redhat.com>
Tue, 15 Dec 2015 00:58:39 +0000 (10:58 +1000)
Previously, the comment was inconsistent. EDEADLK is what the ww_mutex
mechanism really returns.

Signed-off-by: Nicolai Hähnle <Nicolai.Haehnle@amd.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
include/drm/ttm/ttm_bo_driver.h

index 813042cede5728a1bc3e8d463006217d49f35483..3d4bf08aa21fee988c65e51675800c35dc921a8f 100644 (file)
@@ -826,10 +826,10 @@ static inline int __ttm_bo_reserve(struct ttm_buffer_object *bo,
  * reserved, the validation sequence is checked against the validation
  * sequence of the process currently reserving the buffer,
  * and if the current validation sequence is greater than that of the process
- * holding the reservation, the function returns -EAGAIN. Otherwise it sleeps
+ * holding the reservation, the function returns -EDEADLK. Otherwise it sleeps
  * waiting for the buffer to become unreserved, after which it retries
  * reserving.
- * The caller should, when receiving an -EAGAIN error
+ * The caller should, when receiving an -EDEADLK error
  * release all its buffer reservations, wait for @bo to become unreserved, and
  * then rerun the validation with the same validation sequence. This procedure
  * will always guarantee that the process with the lowest validation sequence