|SUCCESS| net/ice: fix storing field offset arg

[dpdklab at iol.unh.edu]

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

_AI Code Review_

=== Patch Review: series.patch (via Claude) ===
Review date: 2026-09-14

# Review of PATCH: net/ice: fix storing field offset arg

## Summary
This patch fixes a type mismatch in the ice driver where a field offset is stored as `uint8_t` but should be stored as `int` to match the actual parameter type. The fix is straightforward and correct.

---

## Correctness Issues

**None found.**

The patch correctly identifies and fixes a type mismatch. The field offset is parsed from a string and stored into a pointer that was incorrectly typed as `uint8_t *` when the target is actually `int`. This could lead to only 1 byte being written when 4 bytes should be written (on typical platforms where `int` is 32 bits), leaving 3 bytes uninitialized.

The fix changes the pointer type to `int *`, which matches the actual type being pointed to.

---

## Style and Format Issues

**None found.**

The patch follows DPDK coding style:
- Proper variable naming (lowercase with underscores)
- Correct indentation
- No trailing whitespace
- The change is minimal and focused

---

## API and Documentation

**Info: Release notes not required**

The commit message indicates this fix is targeted for backport (marked `Cc: stable at dpdk.org` and has a Bugzilla ID). Since this is a bug fix with no API changes, user-visible behavior changes, or new features, release notes are not required.

The patch includes appropriate metadata:
- Bugzilla reference
- Fixes tag with original commit
- Stable CC tag

---

## Additional Observations

**Info: Superseded by kvargs numeric args patchset**

The commit message notes this fix is superseded by a larger patchset that reworks kvargs numeric argument parsing. The standalone fix is provided specifically for backporting to stable branches where the full kvargs rework may not be suitable.

This is good practice for stable maintenance.

---

## Conclusion

**No issues found.** The patch correctly fixes a type mismatch bug. The change is appropriate, well-documented, and suitable for backporting to stable branches.