Claude review: drm: Suppress intentional warning backtraces in scaling unit tests

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

Patch Review

**Clean and correct application of the API**

The suppression wraps the exact call that triggers warnings. The comments explaining why suppression is needed are appropriate, though perhaps a bit verbose for the CLAUDE.md "no comments" guidance (but that doesn't apply to kernel code conventions).

**Suppression covers all parameterized cases, not just error cases**

```c
+	KUNIT_START_SUPPRESSED_WARNING(test);
 	scaling_factor = drm_rect_calc_hscale(&params->src, &params->dst,
 					      params->min_range, params->max_range);
+	KUNIT_END_SUPPRESSED_WARNING(test);
```

This suppresses warnings for ALL parameterized test cases, including those that don't trigger warnings. This is fine (the overhead is negligible and the alternative would be conditional suppression based on `expected_scaling_factor`), but worth noting that the warning count won't always equal 1 for all parameterized cases.

---
Generated by Claude Code Patch Reviewer