From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC v3] cpuidle : Add support for pseudo-cpuidle driver
Date: Tue, 10 Nov 2020 18:28:20 +0800 [thread overview]
Message-ID: <202011101845.mrM3BeEC-lkp@intel.com> (raw)
In-Reply-To: <20201109061612.150441-1-huntbag@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 3641 bytes --]
Hi Abhishek,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on pm/linux-next]
[also build test WARNING on linus/master linux/master v5.10-rc3 next-20201109]
[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]
url: https://github.com/0day-ci/linux/commits/Abhishek-Goel/cpuidle-Add-support-for-pseudo-cpuidle-driver/20201109-142255
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/1fb96577b34f9a7a8ca40bd5f7a8ca712fd2d363
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Abhishek-Goel/cpuidle-Add-support-for-pseudo-cpuidle-driver/20201109-142255
git checkout 1fb96577b34f9a7a8ca40bd5f7a8ca712fd2d363
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sh
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/cpuidle/cpuidle-test.c: In function 'add_cpuidle_states':
>> drivers/cpuidle/cpuidle-test.c:190:6: warning: variable 'rc' set but not used [-Wunused-but-set-variable]
190 | int rc;
| ^~
vim +/rc +190 drivers/cpuidle/cpuidle-test.c
178
179 static int add_cpuidle_states(void)
180 {
181 /* Parse the module param and initialize the idle states here
182 * in cpuidle_state_table.
183 */
184 char *this_param;
185 char *input_name = name;
186 char *input_res = residency_us;
187 char *input_lat = latency_us;
188 int index = 1;
189 long temp;
> 190 int rc;
191
192 switch (sim_type) {
193 case 1:
194 cpuidle_state_table = cpuidle_states_ppc;
195 return 0;
196 case 2:
197 cpuidle_state_table = cpuidle_states_intel;
198 return 0;
199 case 3:
200 break;
201 default:
202 pr_warn("Sim value out of bound\n");
203 break;
204 }
205
206 if (strnlen(input_name, MAX_PARAM_LENGTH)) {
207 while ((this_param = strsep(&input_name, ",")) && index <= nr_states) {
208 strcpy(cpuidle_states[index].name, this_param);
209 cpuidle_states[index].enter = idle_loop;
210 index++;
211 }
212 }
213
214 if (strnlen(input_res, MAX_PARAM_LENGTH)) {
215 index = 1;
216 while ((this_param = strsep(&input_res, ",")) && index <= nr_states) {
217 rc = kstrtol(this_param, 10, &temp);
218 cpuidle_states[index].target_residency = temp;
219 index++;
220 }
221 }
222
223 if (strnlen(input_lat, MAX_PARAM_LENGTH)) {
224 index = 1;
225 while ((this_param = strsep(&input_lat, ",")) && index <= nr_states) {
226 rc = kstrtol(this_param, 10, &temp);
227 cpuidle_states[index].exit_latency = temp;
228 index++;
229 }
230 }
231
232 cpuidle_state_table = cpuidle_states;
233 return nr_states;
234 }
235
---
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: 53530 bytes --]
prev parent reply other threads:[~2020-11-10 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 6:16 [RFC v3] cpuidle : Add support for pseudo-cpuidle driver Abhishek Goel
2020-11-10 10:28 ` kernel test robot [this message]
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=202011101845.mrM3BeEC-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.