From: kernel test robot <lkp@intel.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Raspberry Pi Kernel Maintenance <kernel-list@raspberrypi.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Naushir Patuck <naush@raspberrypi.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: Re: [PATCH v4 3/4] media: raspberrypi: Add support for RP1-CFE
Date: Thu, 5 Sep 2024 18:50:48 +0800 [thread overview]
Message-ID: <202409051822.ZzUGw3XQ-lkp@intel.com> (raw)
In-Reply-To: <20240904-rp1-cfe-v4-3-f1b5b3d69c81@ideasonboard.com>
Hi Tomi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 431c1646e1f86b949fa3685efc50b660a364c2b6]
url: https://github.com/intel-lab-lkp/linux/commits/Tomi-Valkeinen/media-uapi-Add-meta-formats-for-PiSP-FE-config-and-stats/20240904-192729
base: 431c1646e1f86b949fa3685efc50b660a364c2b6
patch link: https://lore.kernel.org/r/20240904-rp1-cfe-v4-3-f1b5b3d69c81%40ideasonboard.com
patch subject: [PATCH v4 3/4] media: raspberrypi: Add support for RP1-CFE
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20240905/202409051822.ZzUGw3XQ-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240905/202409051822.ZzUGw3XQ-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/202409051822.ZzUGw3XQ-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/media/platform/raspberrypi/rp1-cfe/cfe.c:2445:12: warning: 'cfe_runtime_resume' defined but not used [-Wunused-function]
2445 | static int cfe_runtime_resume(struct device *dev)
| ^~~~~~~~~~~~~~~~~~
>> drivers/media/platform/raspberrypi/rp1-cfe/cfe.c:2435:12: warning: 'cfe_runtime_suspend' defined but not used [-Wunused-function]
2435 | static int cfe_runtime_suspend(struct device *dev)
| ^~~~~~~~~~~~~~~~~~~
vim +/cfe_runtime_resume +2445 drivers/media/platform/raspberrypi/rp1-cfe/cfe.c
2434
> 2435 static int cfe_runtime_suspend(struct device *dev)
2436 {
2437 struct platform_device *pdev = to_platform_device(dev);
2438 struct cfe_device *cfe = platform_get_drvdata(pdev);
2439
2440 clk_disable_unprepare(cfe->clk);
2441
2442 return 0;
2443 }
2444
> 2445 static int cfe_runtime_resume(struct device *dev)
2446 {
2447 struct platform_device *pdev = to_platform_device(dev);
2448 struct cfe_device *cfe = platform_get_drvdata(pdev);
2449 int ret;
2450
2451 ret = clk_prepare_enable(cfe->clk);
2452 if (ret) {
2453 dev_err(dev, "Unable to enable clock\n");
2454 return ret;
2455 }
2456
2457 return 0;
2458 }
2459
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-05 10:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 11:19 [PATCH v4 0/4] media: raspberrypi: Support RPi5's CFE Tomi Valkeinen
2024-09-04 11:19 ` [PATCH v4 1/4] media: uapi: Add meta formats for PiSP FE config and stats Tomi Valkeinen
2024-09-04 11:19 ` [PATCH v4 2/4] dt-bindings: media: Add bindings for raspberrypi,rp1-cfe Tomi Valkeinen
2024-09-04 11:19 ` [PATCH v4 3/4] media: raspberrypi: Add support for RP1-CFE Tomi Valkeinen
2024-09-05 10:50 ` kernel test robot [this message]
2024-09-05 11:11 ` Laurent Pinchart
2024-09-09 5:08 ` Tomi Valkeinen
2024-09-09 5:22 ` Tomi Valkeinen
2024-09-09 9:13 ` Jacopo Mondi
2024-09-09 10:04 ` Tomi Valkeinen
2024-09-09 13:29 ` Jacopo Mondi
2024-09-09 13:45 ` Laurent Pinchart
2024-09-09 15:52 ` Sakari Ailus
2024-09-10 9:19 ` Jacopo Mondi
2024-09-10 9:25 ` Sakari Ailus
2024-09-10 9:42 ` Jacopo Mondi
2024-09-10 9:55 ` Sakari Ailus
2024-09-10 10:06 ` Laurent Pinchart
2024-09-10 10:12 ` Tomi Valkeinen
2024-09-10 9:56 ` Tomi Valkeinen
2024-09-10 10:11 ` Laurent Pinchart
2024-09-10 10:21 ` Sakari Ailus
2024-09-10 10:26 ` Tomi Valkeinen
2024-09-10 10:18 ` Jacopo Mondi
2024-09-10 10:28 ` Tomi Valkeinen
2024-09-04 11:19 ` [PATCH v4 4/4] media: admin-guide: Document the Raspberry Pi CFE (rp1-cfe) Tomi Valkeinen
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=202409051822.ZzUGw3XQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kernel-list@raspberrypi.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzk@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=naush@raspberrypi.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox