From: Pavel Machek <pavel@nabladev.com>
To: Chris Brandt <chris.brandt@renesas.com>
Cc: cip-dev@lists.cip-project.org,
Nobuhiro Iwamatsu <nobuhiro.iwamatsu.x90@mail.toshiba>,
Pavel Machek <pavel@nabladev.com>
Subject: Re: [PATCH 5.10.y-cip 05/10] clk: renesas: Use IS_ERR() for pointers that cannot be NULL
Date: Thu, 16 Apr 2026 23:08:05 +0200 [thread overview]
Message-ID: <aeFPtSgi-v1Km1uP@duo.ucw.cz> (raw)
In-Reply-To: <20260415181810.4073807-6-chris.brandt@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
Hi!
> From: Geert Uytterhoeven <geert+renesas@glider.be>
>
> commit 6a636d203cc8d29ae73116bbca8b0ea2c7a90d7f upstream.
>
> The use of IS_ERR_OR_NULL() suggests that "clk" can be a NULL pointer.
> Hence smatch assumes so, and issues a "passing zero to 'PTR_ERR'"
> warning.
>
> At these checkpoints, "clk" always contains either a valid pointer, or
> an error pointer (none of the functions called return NULL pointers).
> Hence replace IS_ERR_OR_NULL() by IS_ERR().
>
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> Closes: https://lore.kernel.org/r/202408032025.ve2JMaoV-lkp@intel.com/
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> Link:
> https://patch.msgid.link/81260328acb5c78e915ab04afad3901a31c16128.1758793709.git.geert+renesas@glider.be
[<-- here -->]
> Signed-off-by: Chris Brandt <chris.brandt@renesas.com>
Apparently, this one is different from upstream. That is okay, but
note saying [dropped this because that] would be welcome before your
signoff.
Thanks and best regards,
Pavel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-04-16 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 18:17 [PATCH 5.10.y-cip 00/10] Add additional support for MIPI-DSI for RZ/G2L Chris Brandt
2026-04-15 18:18 ` [PATCH 5.10.y-cip 01/10] drm: renesas: rz-du: Add atomic_pre_enable Chris Brandt
2026-04-15 18:18 ` [PATCH 5.10.y-cip 02/10] drm: renesas: rz-du: Implement MIPI DSI host transfers Chris Brandt
2026-04-15 18:18 ` [PATCH 5.10.y-cip 03/10] drm: renesas: rz-du: mipi_dsi: fix kernel panic when rebooting for some panels Chris Brandt
2026-04-15 18:18 ` [PATCH 5.10.y-cip 04/10] drm: renesas: rz-du: mipi_dsi: Set DSI divider Chris Brandt
2026-04-15 18:18 ` [PATCH 5.10.y-cip 05/10] clk: renesas: Use IS_ERR() for pointers that cannot be NULL Chris Brandt
2026-04-16 21:08 ` Pavel Machek [this message]
2026-04-17 12:56 ` Chris Brandt
2026-04-15 18:18 ` [PATCH 5.10.y-cip 06/10] clk: renesas: rzg2l: Fix intin variable size Chris Brandt
2026-04-15 18:18 ` [PATCH 5.10.y-cip 07/10] math64: New DIV_U64_ROUND_CLOSEST helper Chris Brandt
2026-04-15 18:18 ` [PATCH 5.10.y-cip 08/10] clk: renesas: rzg2l: Select correct div round macro Chris Brandt
2026-04-15 18:18 ` [PATCH 5.10.y-cip 09/10] clk: renesas: rzg2l: Remove DSI clock rate restrictions Chris Brandt
2026-04-15 18:18 ` [PATCH 5.10.y-cip 10/10] clk: renesas: Add missing log message terminators Chris Brandt
2026-04-16 21:09 ` [cip-dev] [PATCH 5.10.y-cip 00/10] Add additional support for MIPI-DSI for RZ/G2L Pavel Machek
2026-04-17 13:10 ` Chris Brandt
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=aeFPtSgi-v1Km1uP@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=chris.brandt@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
/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