From: Viresh Kumar <viresh.kumar@linaro.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-pm@vger.kernel.org
Subject: Re: [vireshk:opp/genpd-performance-state 14/18] include/linux/pm_qos.h:199:19: warning: 'dev_pm_qos_add_notifier' declared 'static' but never defined
Date: Mon, 9 Jan 2017 08:54:45 +0530 [thread overview]
Message-ID: <20170109032445.GK21926@vireshk-i7> (raw)
In-Reply-To: <201701061954.4iGTmC2m%fengguang.wu@intel.com>
On 06-01-17, 19:32, kbuild test robot wrote:
> tree: https://git.linaro.org/people/vireshk/linux opp/genpd-performance-state
> head: e327d4cbb8b86e33f3e777bbbd8a9a8326e5f6d5
> commit: efd46e263c100a5051c4b9d15f523ce08f76934a [14/18] PM / QOS: Pass request type to dev_pm_qos_{add|remove}_notifier()
> config: openrisc-or1ksim_defconfig (attached as .config)
> compiler: or32-linux-gcc (GCC) 4.5.1-or32-1.0rc1
> 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
> git checkout efd46e263c100a5051c4b9d15f523ce08f76934a
> # save the attached .config to linux build tree
> make.cross ARCH=openrisc
>
> All warnings (new ones prefixed by >>):
>
> In file included from kernel/power/qos.c:32:0:
> include/linux/pm_qos.h:202:4: error: expected identifier or '(' before '{' token
> >> include/linux/pm_qos.h:199:19: warning: 'dev_pm_qos_add_notifier' declared 'static' but never defined
Fixed thanks.
--
viresh
prev parent reply other threads:[~2017-01-09 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 11:32 [vireshk:opp/genpd-performance-state 14/18] include/linux/pm_qos.h:199:19: warning: 'dev_pm_qos_add_notifier' declared 'static' but never defined kbuild test robot
2017-01-09 3:24 ` Viresh Kumar [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=20170109032445.GK21926@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-pm@vger.kernel.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 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).