Re: [PATCH v2 1/1] media: dt-bindings: move ovti,ov2659.txt into ovti,ov8858.yaml

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The commit message subject claims to move the binding into 'ovti,ov8858.yaml', but the patch actually creates 'ovti,ov2659.yaml'.
- [Low] The patch deletes the `.txt` binding but fails to update the reference in the `MAINTAINERS` file.
--

commit 87439fdf072810cc54b017765ea8976dde911644
Author: Frank Li <Frank.Li@nxp.com>

media: dt-bindings: move ovti,ov2659.txt into ovti,ov8858.yaml

Convert the OmniVision OV2659 camera sensor binding from plain text to
YAML schema format.

> media: dt-bindings: move ovti,ov2659.txt into ovti,ov8858.yaml

[Severity: Medium]
The commit message subject claims to move the binding into ovti,ov8858.yaml,
but the patch actually creates ovti,ov2659.yaml. Should the commit title be
updated to match the newly created filename?

> diff --git a/Documentation/devicetree/bindings/media/i2c/ovti,ov2659.txt b/Documentation/devicetree/bindings/media/i2c/ovti,ov2659.txt
> deleted file mode 100644
> index 92989a619f292..0000000000000
> --- a/Documentation/devicetree/bindings/media/i2c/ovti,ov2659.txt
> +++ /dev/null

[Severity: Low]
Does the MAINTAINERS file also need an update?

The patch deletes the text binding ovti,ov2659.txt, but it seems the
OMNIVISION OV2659 SENSOR DRIVER entry in the MAINTAINERS file was not updated
to point to the new ovti,ov2659.yaml file.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260827190501.56673-1-Frank.Li@oss.nxp.com?part=1