All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Mohan Kumar <mohankumar718@gmail.com>
Cc: kbuild-all@01.org, rjw@rjwysocki.net, viresh.kumar@linaro.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: cpufreq: use kstrtoul instead of obsolete simple_strtoul
Date: Sun, 21 Apr 2019 17:14:25 +0800	[thread overview]
Message-ID: <201904211703.iXAE71bW%lkp@intel.com> (raw)
In-Reply-To: <1555669738-3869-1-git-send-email-mohankumar718@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2338 bytes --]

Hi Mohan,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on pm/linux-next]
[also build test ERROR on v5.1-rc5 next-20190418]
[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/Mohan-Kumar/drivers-cpufreq-use-kstrtoul-instead-of-obsolete-simple_strtoul/20190421-044216
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: i386-randconfig-c0-04211526 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>


All errors (new ones prefixed by >>):

   drivers//cpufreq/elanfreq.c: In function 'elanfreq_setup':
>> drivers//cpufreq/elanfreq.c:187:48: error: 'val' undeclared (first use in this function); did you mean 'vmap'?
     max_freq = kstrtoul(str, 0, (unsigned long *)&val);
                                                   ^~~
                                                   vmap
   drivers//cpufreq/elanfreq.c:187:48: note: each undeclared identifier is reported only once for each function it appears in

vim +187 drivers//cpufreq/elanfreq.c

   171	
   172	
   173	#ifndef MODULE
   174	/**
   175	 * elanfreq_setup - elanfreq command line parameter parsing
   176	 *
   177	 * elanfreq command line parameter.  Use:
   178	 *  elanfreq=66000
   179	 * to set the maximum CPU frequency to 66 MHz. Note that in
   180	 * case you do not give this boot parameter, the maximum
   181	 * frequency will fall back to _current_ CPU frequency which
   182	 * might be lower. If you build this as a module, use the
   183	 * max_freq module parameter instead.
   184	 */
   185	static int __init elanfreq_setup(char *str)
   186	{
 > 187		max_freq = kstrtoul(str, 0, (unsigned long *)&val);
   188		pr_warn("You're using the deprecated elanfreq command line option. Use elanfreq.max_freq instead, please!\n");
   189		return 1;
   190	}
   191	__setup("elanfreq=", elanfreq_setup);
   192	#endif
   193	
   194	

---
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: 26885 bytes --]

      reply	other threads:[~2019-04-21  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19 10:28 [PATCH] drivers: cpufreq: use kstrtoul instead of obsolete simple_strtoul Mohan Kumar
2019-04-21  9:14 ` kbuild 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=201904211703.iXAE71bW%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mohankumar718@gmail.com \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.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.