From: kbuild test robot <lkp@intel.com>
To: yuantian.tang@nxp.com
Cc: kbuild-all@01.org, rjw@rjwysocki.net, viresh.kumar@linaro.org,
leoyang.li@nxp.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Tang Yuantian <Yuantian.Tang@nxp.com>,
Scott Wood <scottwood@nxp.com>
Subject: Re: [PATCH 2/2 v2] cpufreq: qoriq: Don't look at clock implementation details
Date: Wed, 8 Feb 2017 19:19:25 +0800 [thread overview]
Message-ID: <201702081937.6pnj3VE2%fengguang.wu@intel.com> (raw)
In-Reply-To: <1486532585-36463-2-git-send-email-yuantian.tang@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 4153 bytes --]
Hi Tang,
[auto build test WARNING on pm/linux-next]
[also build test WARNING on v4.10-rc7 next-20170208]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/yuantian-tang-nxp-com/cpufreq-qoriq-added-arm64-socs-support/20170208-163748
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: arm-multi_v7_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
drivers/cpufreq/qoriq-cpufreq.c: In function 'qoriq_cpufreq_cpu_init':
>> drivers/cpufreq/qoriq-cpufreq.c:230:2: warning: 'pnode' may be used uninitialized in this function [-Wmaybe-uninitialized]
of_node_put(pnode);
^~~~~~~~~~~~~~~~~~
vim +/pnode +230 drivers/cpufreq/qoriq-cpufreq.c
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 214 pr_err("invalid frequency table: %d\n", ret);
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 215 goto err_nomem1;
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 216 }
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 217
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 218 data->table = table;
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 219
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 220 /* update ->cpus if we have cluster, no harm if not */
a4f20742 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2015-03-13 221 set_affected_cpus(policy);
a4f20742 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2015-03-13 222 policy->driver_data = data;
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 223
906fe033 drivers/cpufreq/ppc-corenet-cpufreq.c Ed Swarthout 2014-06-05 224 /* Minimum transition latency is 12 platform clocks */
906fe033 drivers/cpufreq/ppc-corenet-cpufreq.c Ed Swarthout 2014-06-05 225 u64temp = 12ULL * NSEC_PER_SEC;
a4f20742 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2015-03-13 226 do_div(u64temp, get_bus_freq());
906fe033 drivers/cpufreq/ppc-corenet-cpufreq.c Ed Swarthout 2014-06-05 227 policy->cpuinfo.transition_latency = u64temp + 1;
6712d293 drivers/cpufreq/ppc-corenet-cpufreq.c Tim Gardner 2014-04-28 228
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 229 of_node_put(np);
8a95c144 drivers/cpufreq/qoriq-cpufreq.c Tang Yuantian 2015-06-04 @230 of_node_put(pnode);
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 231
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 232 return 0;
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 233
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 234 err_nomem1:
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 235 kfree(table);
8a95c144 drivers/cpufreq/qoriq-cpufreq.c Tang Yuantian 2015-06-04 236 err_pclk:
8a95c144 drivers/cpufreq/qoriq-cpufreq.c Tang Yuantian 2015-06-04 237 kfree(data->pclk);
defa4c73 drivers/cpufreq/ppc-corenet-cpufreq.c Tang Yuantian 2013-06-05 238 err_nomem2:
:::::: The code at line 230 was first introduced by commit
:::::: 8a95c1441c799bb0f0d31cdb11523d91923d51a7 cpufreq: qoriq: optimize the CPU frequency switching time
:::::: TO: Tang Yuantian <Yuantian.Tang@freescale.com>
:::::: CC: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 39884 bytes --]
next prev parent reply other threads:[~2017-02-08 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 5:43 [PATCH 1/2 v2] cpufreq: qoriq: added arm64 socs support yuantian.tang
2017-02-08 5:43 ` [PATCH 2/2 v2] cpufreq: qoriq: Don't look at clock implementation details yuantian.tang
2017-02-08 11:19 ` kbuild test robot [this message]
2017-02-08 20:51 ` [PATCH 1/2 v2] cpufreq: qoriq: added arm64 socs support kbuild test robot
2017-02-09 0:00 ` Rafael J. Wysocki
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=201702081937.6pnj3VE2%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=scottwood@nxp.com \
--cc=viresh.kumar@linaro.org \
--cc=yuantian.tang@nxp.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
all inboxes | Powered by JetHome®