All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tharit Tangkijwanichakul <tharitt97@gmail.com>,
	Nicolas Dufresne <nicolas.dufresne@collabora.com>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	Hans Verkuil <hverkuil@kernel.org>,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
	me@brighamcampbell.com, jkoolstra@xs4all.nl,
	Frank.li@oss.nxp.com,
	Tharit Tangkijwanichakul <tharitt97@gmail.com>
Subject: Re: [PATCH v3] media: hantro: release runtime resources when device_run fails
Date: Thu, 30 Jul 2026 04:37:40 +0800	[thread overview]
Message-ID: <202607300319.RuKrwvI7-lkp@intel.com> (raw)
In-Reply-To: <20260726024243.730-1-tharitt97@gmail.com>

Hi Tharit,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on pza/reset/next v7.2-rc5 next-20260729]
[cannot apply to pza/imx-drm/next]
[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/Tharit-Tangkijwanichakul/media-hantro-release-runtime-resources-when-device_run-fails/20260726-104549
base:   linus/master
patch link:    https://lore.kernel.org/r/20260726024243.730-1-tharitt97%40gmail.com
patch subject: [PATCH v3] media: hantro: release runtime resources when device_run fails
config: nios2-allmodconfig (https://download.01.org/0day-ci/archive/20260730/202607300319.RuKrwvI7-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260730/202607300319.RuKrwvI7-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/202607300319.RuKrwvI7-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/media/platform/verisilicon/hantro_drv.c:1309:12: warning: 'hantro_runtime_suspend' defined but not used [-Wunused-function]
    1309 | static int hantro_runtime_suspend(struct device *dev)
         |            ^~~~~~~~~~~~~~~~~~~~~~
>> drivers/media/platform/verisilicon/hantro_drv.c:1287:12: warning: 'hantro_runtime_resume' defined but not used [-Wunused-function]
    1287 | static int hantro_runtime_resume(struct device *dev)
         |            ^~~~~~~~~~~~~~~~~~~~~


vim +/hantro_runtime_suspend +1309 drivers/media/platform/verisilicon/hantro_drv.c

  1286	
> 1287	static int hantro_runtime_resume(struct device *dev)
  1288	{
  1289		struct hantro_dev *vpu = dev_get_drvdata(dev);
  1290		int ret;
  1291	
  1292		ret = clk_bulk_enable(vpu->variant->num_clocks, vpu->clocks);
  1293		if (ret)
  1294			return ret;
  1295	
  1296		if (vpu->variant->runtime_resume) {
  1297			ret = vpu->variant->runtime_resume(vpu);
  1298			if (ret)
  1299				goto err_disable_clocks;
  1300		}
  1301	
  1302		return 0;
  1303	
  1304	err_disable_clocks:
  1305		clk_bulk_disable(vpu->variant->num_clocks, vpu->clocks);
  1306		return ret;
  1307	}
  1308	
> 1309	static int hantro_runtime_suspend(struct device *dev)
  1310	{
  1311		struct hantro_dev *vpu = dev_get_drvdata(dev);
  1312	
  1313		clk_bulk_disable(vpu->variant->num_clocks, vpu->clocks);
  1314		return 0;
  1315	}
  1316	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Tharit Tangkijwanichakul <tharitt97@gmail.com>,
	Nicolas Dufresne <nicolas.dufresne@collabora.com>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	Hans Verkuil <hverkuil@kernel.org>,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
	me@brighamcampbell.com, jkoolstra@xs4all.nl,
	Frank.li@oss.nxp.com,
	Tharit Tangkijwanichakul <tharitt97@gmail.com>
Subject: Re: [PATCH v3] media: hantro: release runtime resources when device_run fails
Date: Thu, 30 Jul 2026 04:37:40 +0800	[thread overview]
Message-ID: <202607300319.RuKrwvI7-lkp@intel.com> (raw)
In-Reply-To: <20260726024243.730-1-tharitt97@gmail.com>

Hi Tharit,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on pza/reset/next v7.2-rc5 next-20260729]
[cannot apply to pza/imx-drm/next]
[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/Tharit-Tangkijwanichakul/media-hantro-release-runtime-resources-when-device_run-fails/20260726-104549
base:   linus/master
patch link:    https://lore.kernel.org/r/20260726024243.730-1-tharitt97%40gmail.com
patch subject: [PATCH v3] media: hantro: release runtime resources when device_run fails
config: nios2-allmodconfig (https://download.01.org/0day-ci/archive/20260730/202607300319.RuKrwvI7-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260730/202607300319.RuKrwvI7-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/202607300319.RuKrwvI7-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/media/platform/verisilicon/hantro_drv.c:1309:12: warning: 'hantro_runtime_suspend' defined but not used [-Wunused-function]
    1309 | static int hantro_runtime_suspend(struct device *dev)
         |            ^~~~~~~~~~~~~~~~~~~~~~
>> drivers/media/platform/verisilicon/hantro_drv.c:1287:12: warning: 'hantro_runtime_resume' defined but not used [-Wunused-function]
    1287 | static int hantro_runtime_resume(struct device *dev)
         |            ^~~~~~~~~~~~~~~~~~~~~


vim +/hantro_runtime_suspend +1309 drivers/media/platform/verisilicon/hantro_drv.c

  1286	
> 1287	static int hantro_runtime_resume(struct device *dev)
  1288	{
  1289		struct hantro_dev *vpu = dev_get_drvdata(dev);
  1290		int ret;
  1291	
  1292		ret = clk_bulk_enable(vpu->variant->num_clocks, vpu->clocks);
  1293		if (ret)
  1294			return ret;
  1295	
  1296		if (vpu->variant->runtime_resume) {
  1297			ret = vpu->variant->runtime_resume(vpu);
  1298			if (ret)
  1299				goto err_disable_clocks;
  1300		}
  1301	
  1302		return 0;
  1303	
  1304	err_disable_clocks:
  1305		clk_bulk_disable(vpu->variant->num_clocks, vpu->clocks);
  1306		return ret;
  1307	}
  1308	
> 1309	static int hantro_runtime_suspend(struct device *dev)
  1310	{
  1311		struct hantro_dev *vpu = dev_get_drvdata(dev);
  1312	
  1313		clk_bulk_disable(vpu->variant->num_clocks, vpu->clocks);
  1314		return 0;
  1315	}
  1316	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  parent reply	other threads:[~2026-07-29 20:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 11:15 [PATCH] media: hantro: release runtime resources when device_run fails Tharit Tangkijwanichakul
2026-07-24 11:15 ` Tharit Tangkijwanichakul
2026-07-24 11:38 ` Philipp Zabel
2026-07-24 11:38   ` Philipp Zabel
2026-07-24 12:44   ` Tharit Tangkijwanichakul
2026-07-24 12:44     ` Tharit Tangkijwanichakul
2026-07-24 13:12     ` [PATCH v2] " Tharit Tangkijwanichakul
2026-07-24 13:12       ` Tharit Tangkijwanichakul
2026-07-26  2:42       ` [PATCH v3] " Tharit Tangkijwanichakul
2026-07-26  2:42         ` Tharit Tangkijwanichakul
2026-07-27 15:18         ` Frank Li
2026-07-27 15:18           ` Frank Li
2026-07-28  4:30           ` Tharit Tangkijwanichakul
2026-07-28  4:30             ` Tharit Tangkijwanichakul
2026-07-28  4:59         ` [PATCH v4] " Tharit Tangkijwanichakul
2026-07-28  4:59           ` Tharit Tangkijwanichakul
2026-07-28 15:53         ` [PATCH v3] " Frank Li
2026-07-28 15:53           ` Frank Li
2026-07-29  5:59           ` Tharit Tangkijwanichakul
2026-07-29  5:59             ` Tharit Tangkijwanichakul
2026-07-29 20:37         ` kernel test robot [this message]
2026-07-29 20:37           ` kernel test robot
2026-07-24 16:12 ` [PATCH] " Frank Li
2026-07-24 16:12   ` Frank Li
2026-07-25  8:00   ` Tharit Tangkijwanichakul
2026-07-25  8:00     ` Tharit Tangkijwanichakul

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=202607300319.RuKrwvI7-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Frank.li@oss.nxp.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=hverkuil@kernel.org \
    --cc=jkoolstra@xs4all.nl \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mchehab@kernel.org \
    --cc=me@brighamcampbell.com \
    --cc=nicolas.dufresne@collabora.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=p.zabel@pengutronix.de \
    --cc=skhan@linuxfoundation.org \
    --cc=tharitt97@gmail.com \
    /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.