|SUCCESS| net/mlx5: log Rx queue CQ number

[dpdklab at iol.unh.edu]

Test-Label: ai-code-review
Test-Status: SUCCESS
https://dpdk.org/patch/171822

_AI Code Review_

=== Patch Review: series.patch (via Claude) ===
Review date: 2026-10-21

# DPDK Patch Review

## ERRORS

None.

## WARNINGS

None.

## INFO

**Style observation - line length:**
The added log line at line 529:
```c
DRV_LOG(DEBUG, "Port %u Rx queue %u cqn=%u", port_id, rxq->idx, rxq_data->cqn);
```
is 92 characters, which is acceptable (under 100-character limit for readability).

**Missing variable declaration in visible context:**
The patch adds a reference to `port_id` in the log statement, but `port_id` is not visible in the diff context. While this is likely defined earlier in the function `mlx5_rxq_create_devx_cq_resources()`, the evidence rule means I cannot verify this without reading the full function. If `port_id` is not in scope, this would be a compilation error, but I cannot make that determination from the patch alone.

However, given that:
- The patch has an "Acked-by" from a maintainer
- The pattern `DRV_LOG(DEBUG, "Port %u ...")` is idiomatic in DPDK drivers
- The function name suggests it operates on an `rxq` which typically contains port information

it is reasonable to assume `port_id` is available in the function scope. This would need to be verified by compilation, which is outside the scope of this review per the evidence rule.

**Documentation and release notes:**
This is a debug logging enhancement that does not change API, ABI, or user-visible behavior (debug logs are not part of the stable interface). No release notes are required.

---

Review-Result: CLEAN