From: Hans de Goede <hdegoede@redhat.com>
To: "kernel test robot" <lkp@intel.com>,
"Thomas Weißschuh" <linux@weissschuh.net>
Cc: kbuild-all@lists.01.org,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Thomas Koch" <linrunner@gmx.net>,
"Nicolò Piazzalunga" <nicolopiazzalunga@gmail.com>
Subject: Re: [linux-next:master 8287/11475] drivers/platform/x86/thinkpad_acpi.c:9600:9: error: implicit declaration of function 'power_supply_charge_behaviour_show'
Date: Sat, 8 Jan 2022 11:24:47 +0100 [thread overview]
Message-ID: <487dd7a3-8f29-de9a-2612-65fe895e676f@redhat.com> (raw)
In-Reply-To: <202201080424.U284YcVw-lkp@intel.com>
Hi,
On 1/7/22 21:08, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: b8170452cd5121b11a5726e3ea8dbdfc2d74e771
> commit: b55d416d48f5907f66218ae3d878e3bfb69ae4e6 [8287/11475] platform/x86: thinkpad_acpi: support force-discharge
> config: x86_64-buildonly-randconfig-r005-20220107 (https://download.01.org/0day-ci/archive/20220108/202201080424.U284YcVw-lkp@intel.com/config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b55d416d48f5907f66218ae3d878e3bfb69ae4e6
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout b55d416d48f5907f66218ae3d878e3bfb69ae4e6
> # save the config file to linux build tree
> mkdir build_dir
> make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/platform/x86/
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> drivers/platform/x86/thinkpad_acpi.c: In function 'charge_behaviour_show':
>>> drivers/platform/x86/thinkpad_acpi.c:9600:9: error: implicit declaration of function 'power_supply_charge_behaviour_show' [-Werror=implicit-function-declaration]
> 9600 | return power_supply_charge_behaviour_show(dev, available, active, buf);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> drivers/platform/x86/thinkpad_acpi.c: In function 'charge_behaviour_store':
>>> drivers/platform/x86/thinkpad_acpi.c:9627:13: error: implicit declaration of function 'power_supply_charge_behaviour_parse' [-Werror=implicit-function-declaration]
> 9627 | selected = power_supply_charge_behaviour_parse(available, buf);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
Ok, so this is caused by the config used by this test having the following:
# CONFIG_SYSFS is not set
Thomas, can you do a patch adding static inline stubs for these 2 functions
to include/linux/power_supply.h ? Like it is done for the:
power_supply_add_hwmon_sysfs()
power_supply_remove_hwmon_sysfs()
Just above the declaration of these 2 functions.
Regards,
Hans
next prev parent reply other threads:[~2022-01-08 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 20:08 kernel test robot
2022-01-08 10:24 ` Hans de Goede [this message]
2022-01-08 15:31 ` [PATCH] power: supply: Provide stubs for charge_behaviour helpers Thomas Weißschuh
2022-01-08 15:58 ` Hans de Goede
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=487dd7a3-8f29-de9a-2612-65fe895e676f@redhat.com \
--to=hdegoede@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linrunner@gmx.net \
--cc=linux-mm@kvack.org \
--cc=linux@weissschuh.net \
--cc=lkp@intel.com \
--cc=nicolopiazzalunga@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox