Claude review: drm/i915/display: Make fence timeout infinite

[Claude Code Review Bot <claude-review@example.com>]

Patch Review

Switches from `i915_fence_timeout()` (10 seconds) to `MAX_SCHEDULE_TIMEOUT` (infinite). The commit message itself expresses uncertainty:

> "I'm not actually convinced we want an infinite timeout here because the fence could be from an entirely different device/driver"

This is a valid concern. With the reset fence mechanism from patch 5, the GPU-hung case is handled, but fences from other drivers (e.g., in multi-GPU or import scenarios) would cause an infinite hang with no recovery. The author notes this is for CI experimentation.

**This patch should not be merged as-is** — the commit message says as much. For production, a generous-but-finite timeout (or the existing 10s) would be safer, perhaps with the reset fence providing the fast-path escape from GPU hangs.

One note: if this does go in, the `ret <= 0` check after `dma_fence_wait_any_timeout` with `MAX_SCHEDULE_TIMEOUT` means `ret == 0` (timeout) can never happen, so only `ret < 0` (signal interrupted, which can't happen with `intr=false`) would break. Effectively the loop becomes unbreakable except by fence completion — which is the intent.

---
Generated by Claude Code Patch Reviewer