From: kernel test robot <lkp@intel.com>
To: Matus Gajdos <matuszpd@gmail.com>, Pavel Machek <pavel@ucw.cz>,
Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Matus Gajdos <matuszpd@gmail.com>
Subject: Re: [PATCH 3/3] leds: Add Broadchip BCT3024 LED driver
Date: Fri, 28 Jul 2023 12:20:08 +0800 [thread overview]
Message-ID: <202307281212.NIwa5Cab-lkp@intel.com> (raw)
In-Reply-To: <20230727160525.23312-4-matuszpd@gmail.com>
Hi Matus,
kernel test robot noticed the following build errors:
[auto build test ERROR on robh/for-next]
[also build test ERROR on lee-leds/for-leds-next linus/master v6.5-rc3 next-20230727]
[cannot apply to pavel-leds/for-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/Matus-Gajdos/dt-bindings-Add-vendor-prefix-for-Broadchip-Technology-Group-Co-Ltd/20230728-001607
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20230727160525.23312-4-matuszpd%40gmail.com
patch subject: [PATCH 3/3] leds: Add Broadchip BCT3024 LED driver
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20230728/202307281212.NIwa5Cab-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230728/202307281212.NIwa5Cab-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/202307281212.NIwa5Cab-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/device.h:25,
from include/linux/acpi.h:14,
from include/linux/i2c.h:13,
from drivers/leds/leds-bct3024.c:8:
>> drivers/leds/leds-bct3024.c:538:28: error: 'bct3024_runtime_suspend' undeclared here (not in a function); did you mean 'pm_runtime_suspend'?
538 | SET_RUNTIME_PM_OPS(bct3024_runtime_suspend, bct3024_runtime_resume,
| ^~~~~~~~~~~~~~~~~~~~~~~
include/linux/pm.h:337:28: note: in definition of macro 'RUNTIME_PM_OPS'
337 | .runtime_suspend = suspend_fn, \
| ^~~~~~~~~~
drivers/leds/leds-bct3024.c:538:9: note: in expansion of macro 'SET_RUNTIME_PM_OPS'
538 | SET_RUNTIME_PM_OPS(bct3024_runtime_suspend, bct3024_runtime_resume,
| ^~~~~~~~~~~~~~~~~~
>> drivers/leds/leds-bct3024.c:538:53: error: 'bct3024_runtime_resume' undeclared here (not in a function); did you mean 'pm_runtime_resume'?
538 | SET_RUNTIME_PM_OPS(bct3024_runtime_suspend, bct3024_runtime_resume,
| ^~~~~~~~~~~~~~~~~~~~~~
include/linux/pm.h:338:27: note: in definition of macro 'RUNTIME_PM_OPS'
338 | .runtime_resume = resume_fn, \
| ^~~~~~~~~
drivers/leds/leds-bct3024.c:538:9: note: in expansion of macro 'SET_RUNTIME_PM_OPS'
538 | SET_RUNTIME_PM_OPS(bct3024_runtime_suspend, bct3024_runtime_resume,
| ^~~~~~~~~~~~~~~~~~
>> drivers/leds/leds-bct3024.c:539:28: error: 'bct3024_runtime_idle' undeclared here (not in a function); did you mean 'pm_runtime_idle'?
539 | bct3024_runtime_idle)
| ^~~~~~~~~~~~~~~~~~~~
include/linux/pm.h:339:25: note: in definition of macro 'RUNTIME_PM_OPS'
339 | .runtime_idle = idle_fn,
| ^~~~~~~
drivers/leds/leds-bct3024.c:538:9: note: in expansion of macro 'SET_RUNTIME_PM_OPS'
538 | SET_RUNTIME_PM_OPS(bct3024_runtime_suspend, bct3024_runtime_resume,
| ^~~~~~~~~~~~~~~~~~
vim +538 drivers/leds/leds-bct3024.c
536
537 static const struct dev_pm_ops bct3024_pm_ops = {
> 538 SET_RUNTIME_PM_OPS(bct3024_runtime_suspend, bct3024_runtime_resume,
> 539 bct3024_runtime_idle)
540 SET_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend, pm_runtime_force_resume)
541 };
542
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-07-28 4:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 16:05 [PATCH 0/3] leds: Add Broadchip BCT3024 LED driver Matus Gajdos
2023-07-27 16:05 ` [PATCH 1/3] dt-bindings: Add vendor prefix for Broadchip Technology Group Co., Ltd Matus Gajdos
2023-07-28 7:29 ` Krzysztof Kozlowski
2023-07-27 16:05 ` [PATCH 2/3] dt-bindings: leds: Add binding for Broadchip BCT3024 LED driver Matus Gajdos
2023-07-28 7:31 ` Krzysztof Kozlowski
2023-07-27 16:05 ` [PATCH 3/3] leds: Add " Matus Gajdos
2023-07-28 4:20 ` kernel test robot [this message]
2023-07-28 7:41 ` Krzysztof Kozlowski
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=202307281212.NIwa5Cab-lkp@intel.com \
--to=lkp@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=matuszpd@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).