From: sashiko-bot@kernel.org
To: "Benjamin Gaignard" <benjamin.gaignard@collabora.com>
Cc: conor+dt@kernel.org, Frank.Li@kernel.org, imx@lists.linux.dev,
media-ci@linuxtv.org, robh@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/3] media: verisilicon: Remove useless internal fields
Date: Thu, 24 Sep 2026 13:13:46 +0000 [thread overview]
Message-ID: <20260924131347.33A991F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260924130453.196299-4-benjamin.gaignard@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] media: verisilicon: Leftover kernel-doc for removed ctrl_base
--
commit b8008458c58918377e3aa39a0a58310073146cb2
Author: Benjamin Gaignard <benjamin.gaignard@collabora.com>
media: verisilicon: Remove useless internal fields
This commit removes unused fields from struct hantro_variant and struct
hantro_dev because no variants are using multiple registers regions.
This simplifies the driver code.
> diff --git a/drivers/media/platform/verisilicon/hantro.h b/drivers/media/platform/verisilicon/hantro.h
> --- a/drivers/media/platform/verisilicon/hantro.h
> +++ b/drivers/media/platform/verisilicon/hantro.h
[ ... ]
> @@ -184,7 +180,7 @@ hantro_vdev_to_func(struct video_device *vdev)
> * dev_ macros.
> * @clocks: Array of clock handles.
> * @resets: Array of reset handles.
> - * @reg_bases: Mapped addresses of VPU registers.
> + * @reg_base: Mapped address of VPU registers.
> * @enc_base: Mapped address of VPU encoder register for convenience.
> * @dec_base: Mapped address of VPU decoder register for convenience.
> * @ctrl_base: Mapped address of VPU control block.
[Severity: Low]
Should the @ctrl_base kernel-doc be removed as well? The ctrl_base field is
removed from struct hantro_dev below, which leaves this documentation stale
and causes a kernel-doc warning.
> @@ -204,10 +200,9 @@ struct hantro_dev {
> struct device *dev;
> struct clk_bulk_data *clocks;
> struct reset_control *resets;
> - void __iomem **reg_bases;
> + void __iomem *reg_base;
> void __iomem *enc_base;
> void __iomem *dec_base;
> - void __iomem *ctrl_base;
>
> struct mutex vpu_mutex; /* video_device lock */
> spinlock_t irqlock;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260924130453.196299-1-benjamin.gaignard@collabora.com?part=3
next prev parent reply other threads:[~2026-09-24 13:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:04 [PATCH v3 0/3] Remove unused variant and code clean up Benjamin Gaignard
2026-09-24 13:04 ` [PATCH v3 1/3] media: verisilicon: Remove deprecated variant Benjamin Gaignard
2026-09-24 13:18 ` sashiko-bot
2026-09-24 14:16 ` Frank Li
2026-09-24 13:04 ` [PATCH v3 2/3] media: dt-bindings: media: nxp, imx8mq-vpu: Remove nxp,imx8mq-vpu Benjamin Gaignard
2026-09-24 13:10 ` sashiko-bot
2026-09-24 14:19 ` Frank Li
2026-09-24 16:55 ` Conor Dooley
2026-09-24 17:51 ` Nicolas Dufresne
2026-09-25 16:51 ` Conor Dooley
2026-09-24 13:04 ` [PATCH v3 3/3] media: verisilicon: Remove useless internal fields Benjamin Gaignard
2026-09-24 13:13 ` sashiko-bot [this message]
2026-09-24 14:19 ` Frank Li
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=20260924131347.33A991F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=benjamin.gaignard@collabora.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