Lines Matching refs:error
39 * Helper macro to get dx_ctx_node if available otherwise print an error
166 * @backoff: Whether this is part of the error path and binding state changes
296 * Returns: 0 on success. Negative error code on failure. Typical error codes
349 * Returns: Zero on success. Negative error code on failure.
385 * Returns 0 if success, negative error code otherwise.
415 * return an -EINVAL error pointer.
417 * Returns: Unreferenced pointer to the resource on success, negative error
3011 * old streamoutput define command. Return without an error.
3093 * old streamoutput define command. Return without an error.
3639 VMW_DEBUG_USER("SVGA3D command: %d failed with error %d\n",
3772 VMW_DEBUG_USER("Fence submission error. Syncing.\n");
3802 * @sync_file: Only used to clean up in case of an error in this function.
3805 * user-space struct drm_vmw_fence_rep::error member is hopefully left
3806 * untouched, and if it's preloaded with an -EFAULT by user-space, the error
3826 fence_rep.error = ret;
3839 * fence_rep::error filled in. Typically user-space would have pre-set
3849 if (unlikely(ret != 0) && (fence_rep.error == 0)) {
3852 VMW_DEBUG_USER("Fence copy error. Syncing.\n");
3945 * If an error is encountered, the function will return a pointer error value.
3947 * -ERESTARTSYS casted to a pointer error value.
4168 * This error is harmless, because if fence submission fails,
4169 * vmw_fifo_send_fence will sync. The error will be propagated to
4173 VMW_DEBUG_USER("Fence submission error. Syncing.\n");
4273 * normal way to do this hits an error, which should typically be extremely