From: kernel test robot <lkp@intel.com>
To: Wentao Liang <vulab@iscas.ac.cn>,
linux@armlinux.org.uk, airlied@gmail.com, simona@ffwll.ch
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Wentao Liang <vulab@iscas.ac.cn>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/armada: fix device_node reference leak in armada_lcd_bind()
Date: Thu, 14 May 2026 14:27:29 +0800 [thread overview]
Message-ID: <202605141402.WTQDmspg-lkp@intel.com> (raw)
In-Reply-To: <20260509091821.963513-1-vulab@iscas.ac.cn>
Hi Wentao,
kernel test robot noticed the following build errors:
[auto build test ERROR on daeinki-drm-exynos/exynos-drm-next]
[also build test ERROR on drm/drm-next drm-i915/for-linux-next drm-i915/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip linus/master rmk-arm/drm-armada-devel v7.1-rc3 next-20260508]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Wentao-Liang/drm-armada-fix-device_node-reference-leak-in-armada_lcd_bind/20260512-194755
base: https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next
patch link: https://lore.kernel.org/r/20260509091821.963513-1-vulab%40iscas.ac.cn
patch subject: [PATCH] drm/armada: fix device_node reference leak in armada_lcd_bind()
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20260514/202605141402.WTQDmspg-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260514/202605141402.WTQDmspg-lkp@intel.com/reproduce)
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
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202605141402.WTQDmspg-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/armada/armada_crtc.c: In function 'armada_lcd_bind':
>> drivers/gpu/drm/armada/armada_crtc.c:1039:9: error: 'ret' undeclared (first use in this function); did you mean 'res'?
1039 | ret = armada_drm_crtc_create(drm, dev, res, irq, variant, port);
| ^~~
| res
drivers/gpu/drm/armada/armada_crtc.c:1039:9: note: each undeclared identifier is reported only once for each function it appears in
vim +1039 drivers/gpu/drm/armada/armada_crtc.c
1007
1008 static int
1009 armada_lcd_bind(struct device *dev, struct device *master, void *data)
1010 {
1011 struct platform_device *pdev = to_platform_device(dev);
1012 struct drm_device *drm = data;
1013 struct resource *res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
1014 int irq = platform_get_irq(pdev, 0);
1015 const struct armada_variant *variant;
1016 struct device_node *port = NULL;
1017 struct device_node *np, *parent = dev->of_node;
1018
1019 if (irq < 0)
1020 return irq;
1021
1022
1023 variant = device_get_match_data(dev);
1024 if (!variant)
1025 return -ENXIO;
1026
1027 if (parent) {
1028 np = of_get_child_by_name(parent, "ports");
1029 if (np)
1030 parent = np;
1031 port = of_get_child_by_name(parent, "port");
1032 of_node_put(np);
1033 if (!port) {
1034 dev_err(dev, "no port node found in %pOF\n", parent);
1035 return -ENXIO;
1036 }
1037 }
1038
> 1039 ret = armada_drm_crtc_create(drm, dev, res, irq, variant, port);
1040 if (ret)
1041 of_node_put(port);
1042 return ret;
1043 }
1044
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-05-14 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 9:18 [PATCH] drm/armada: fix device_node reference leak in armada_lcd_bind() Wentao Liang
2026-05-12 21:49 ` kernel test robot
2026-05-13 2:52 ` kernel test robot
2026-05-14 6:27 ` kernel test robot [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=202605141402.WTQDmspg-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.