From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: media-ci@linuxtv.org, robh@kernel.org, Frank.Li@kernel.org,
imx@lists.linux.dev, devicetree@vger.kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH v3 1/1] media: dt-bindings: convert ovti,ov2659.txt to yaml format
Date: Mon, 31 Aug 2026 18:56:22 +0000 [thread overview]
Message-ID: <20260831185622.C41C81F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260831161121.4048134-1-Frank.Li@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Dangling reference in MAINTAINERS file due to renamed binding.
--
commit 86f22844bc16fc2237e1a2e032a70e273a8be8f0
Author: Frank Li <Frank.Li@nxp.com>
media: dt-bindings: convert ovti,ov2659.txt to yaml format
Convert the OmniVision OV2659 camera sensor binding from plain text to
YAML schema format.
> 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 this file deletion need to be accompanied by an update to the MAINTAINERS
file? The OV2659 OMNIVISION SENSOR DRIVER section currently references this
deleted .txt file, which will result in tools like get_maintainer.pl parsing a
dangling reference and potentially missing routing updates for the new YAML
file:
MAINTAINERS:
OV2659 OMNIVISION SENSOR DRIVER
...
F: Documentation/devicetree/bindings/media/i2c/ovti,ov2659.txt
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260831161121.4048134-1-Frank.Li@oss.nxp.com?part=1
prev parent reply other threads:[~2026-08-31 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 16:11 [PATCH v3 1/1] media: dt-bindings: convert ovti,ov2659.txt to yaml format Frank.Li
2026-08-31 18:56 ` sashiko-bot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260831185622.C41C81F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=Frank.Li@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=media-ci@linuxtv.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox