Claude review: drm/gpusvm: Drop redundant @flags.* kernel-doc on struct drm_gpusvm_pages

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

Patch Review

**Correctness:** The change is correct. Looking at the kernel tree, `struct drm_gpusvm_pages_flags` already has its own complete kernel-doc block (lines 108–117 in the header) documenting all five bit-flags (`@migrate_devmem`, `@unmapped`, `@partial_unmap`, `@has_devmem_pages`, `@has_dma_mapping`) plus `@__flags`. The dotted `@flags.*` entries in `struct drm_gpusvm_pages` were purely redundant.

**Replacement text is appropriate:** The new line:
```
 * @flags: Flags for the range; see &struct drm_gpusvm_pages_flags
```
uses the standard kernel-doc cross-reference syntax (`&struct ...`), which will produce a proper hyperlink in generated documentation. This is the idiomatic way to handle named sub-struct types.

**Minor nit (non-blocking):** The original `@flags` description said "Flags for range" and the replacement says "Flags for the range". This is fine — actually slightly more grammatical. However, the canonical doc in `struct drm_gpusvm_pages_flags` itself uses "pages" terminology (e.g., "Flag indicating if the pages has been unmapped"), while this says "range". Both are arguably correct since `drm_gpusvm_pages` is embedded in `drm_gpusvm_range`, but "Flags for the pages" would be more consistent with the naming of both the containing struct (`drm_gpusvm_pages`) and the flags struct (`drm_gpusvm_pages_flags`). This is purely cosmetic and not worth blocking on.

**No other concerns.** The diff is minimal, touches only documentation, and introduces no functional change.

Reviewed-by worthy as-is.

---
Generated by Claude Code Patch Reviewer