From: kernel test robot <lkp@intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>, rui.zhang@intel.com
Cc: kbuild-all@lists.01.org, srinivas.pandruvada@linux.intel.com,
rkumbako@codeaurora.org, amit.kucheria@linaro.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 4/4] thermal: core: Add notifications call in the framework
Date: Sat, 4 Jul 2020 01:03:36 +0800 [thread overview]
Message-ID: <202007040004.UIFUl96J%lkp@intel.com> (raw)
In-Reply-To: <20200703085309.32166-4-daniel.lezcano@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]
Hi Daniel,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linux/master]
[also build test WARNING on linus/master v5.8-rc3 next-20200703]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Daniel-Lezcano/thermal-core-Add-helpers-to-browse-the-cdev-tz-and-governor-list/20200703-165448
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 9ebcfadb0610322ac537dd7aa5d9cbc2b2894c68
config: i386-randconfig-s002-20200702 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-3-gfa153962-dirty
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/thermal/thermal_helpers.c:178:6: sparse: sparse: symbol 'thermal_cdev_set_cur_state' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34858 bytes --]
next prev parent reply other threads:[~2020-07-03 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 8:53 [PATCH v3 1/4] thermal: core: Add helpers to browse the cdev, tz and governor list Daniel Lezcano
2020-07-03 8:53 ` [PATCH v3 2/4] thermal: core: Get thermal zone by id Daniel Lezcano
2020-07-03 8:53 ` [PATCH v3 3/4] thermal: core: genetlink support for events/cmd/sampling Daniel Lezcano
2020-07-03 9:28 ` Amit Kucheria
2020-07-05 6:03 ` Zhang Rui
2020-07-05 10:54 ` Daniel Lezcano
2020-07-06 7:04 ` Daniel Lezcano
2020-07-03 8:53 ` [PATCH v3 4/4] thermal: core: Add notifications call in the framework Daniel Lezcano
2020-07-03 9:30 ` Amit Kucheria
2020-07-03 17:03 ` kernel test robot [this message]
2020-07-03 17:03 ` [RFC PATCH] thermal: core: thermal_cdev_set_cur_state() can be static kernel test robot
2020-07-03 9:14 ` [PATCH v3 1/4] thermal: core: Add helpers to browse the cdev, tz and governor list Amit Kucheria
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=202007040004.UIFUl96J%lkp@intel.com \
--to=lkp@intel.com \
--cc=amit.kucheria@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rkumbako@codeaurora.org \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.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;
as well as URLs for NNTP newsgroup(s).