From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: "kernel test robot" <lkp@intel.com>,
"Luca Ceresoli" <luca.ceresoli@bootlin.com>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
"Linus Walleij" <linusw@kernel.org>,
"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
"Louis Chauvet" <louis.chauvet@bootlin.com>
Subject: Re: drivers/gpu/drm/renesas/rcar-du/rcar_du_encoder.c:72:6-12: inconsistent IS_ERR and PTR_ERR on line 73.
Date: Tue, 06 Oct 2026 11:14:09 +0200 [thread overview]
Message-ID: <DLXN2NHRB139.7OA9W663817Y@bootlin.com> (raw)
In-Reply-To: <202610060853.t5Q4BX8P-lkp@intel.com>
Hello,
On Tue Oct 6, 2026 at 8:40 AM CEST, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 2c3418fffa9d037b2038a6db48be63f9e2291806
> commit: 5b03d4907db93627ef48396f39c3455ce644c946 drm: rcar-du: encoder: convert to of_drm_find_and_get_bridge()
> date: 6 months ago
> config: sparc64-randconfig-r2106-20261005 (https://download.01.org/0day-ci/archive/20261006/202610060853.t5Q4BX8P-lkp@intel.com/config)
> compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 195c81658995a4b7531c30a12c5aef6cf2bbd671)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Fixes: 5b03d4907db9 ("drm: rcar-du: encoder: convert to of_drm_find_and_get_bridge()")
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202610060853.t5Q4BX8P-lkp@intel.com/
>
> cocci warnings: (new ones prefixed by >>)
>>> drivers/gpu/drm/renesas/rcar-du/rcar_du_encoder.c:72:6-12: inconsistent IS_ERR and PTR_ERR on line 73.
...
> 9a248605980a75 drivers/gpu/drm/rcar-du/rcar_du_encoder.c Laurent Pinchart 2020-12-03 @72 if (IS_ERR(bridge))
> 5b03d4907db936 drivers/gpu/drm/renesas/rcar-du/rcar_du_encoder.c Luca Ceresoli 2026-04-09 @73 return PTR_ERR(no_free_ptr(bridge));
This looks like a false positive to me. I guess this code would not trigger
any warning without the infixed no_free_ptr(). But no_free_ptr(p) is
transparent in the sense that it returns a copy of p.
So I guess no fix is needed for this driver. Just let me know in case I'm
wrong.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-10-06 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 6:40 kernel test robot
2026-10-06 9:14 ` Luca Ceresoli [this message]
2026-10-06 10:21 ` Laurent Pinchart
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=DLXN2NHRB139.7OA9W663817Y@bootlin.com \
--to=luca.ceresoli@bootlin.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=louis.chauvet@bootlin.com \
--cc=oe-kbuild-all@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
all inboxes | Powered by JetHome®