From: jonghwa3.lee@samsung.com
To: kernel-janitors@vger.kernel.org
Subject: Re: [samsung:devfreq-for-next 3/5] drivers/devfreq/devfreq.c:75:5: sparse: symbol 'devfreq_get_freq_
Date: Fri, 31 Aug 2012 06:57:41 +0000 [thread overview]
Message-ID: <50406065.1040902@samsung.com> (raw)
In-Reply-To: <20120831065402.GA6761@localhost>
On 2012년 08월 31일 15:54, Fengguang Wu wrote:
> Hi Jonghwa,
>
> FYI, there are new sparse warnings show up in
>
> tree: git://git.infradead.org/users/kmpark/linux-samsung devfreq-for-next
> head: 90609cd121f47446e6a04862214423dbc75bd493
> commit: 4b77f78761889635ba1abd2f4ec1e7f45012e48c [3/5] devfreq: Add sysfs node for representing frequency transition information.
>
> All sparse warnings:
>
> + drivers/devfreq/devfreq.c:75:5: sparse: symbol 'devfreq_get_freq_level' was not declared. Should it be static?
> + drivers/devfreq/devfreq.c:86:5: sparse: symbol 'devfreq_update_status' was not declared. Should it be static?
>
> vim +75 drivers/devfreq/devfreq.c
> 72 return ERR_PTR(-ENODEV);
> 73 }
> 74
> > 75 int devfreq_get_freq_level(struct devfreq *devfreq, unsigned long freq)
> 76 {
> 77 int lev;
> 78
>
> Please consider folding the attached diff :-)
>
Okay, I'll updated it.
> ---
> 0-DAY kernel build testing backend Open Source Technology Centre
> Fengguang Wu <wfg@linux.intel.com> Intel Corporation
prev parent reply other threads:[~2012-08-31 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 6:54 [samsung:devfreq-for-next 3/5] drivers/devfreq/devfreq.c:75:5: sparse: symbol 'devfreq_get_freq_leve Fengguang Wu
2012-08-31 6:57 ` jonghwa3.lee [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=50406065.1040902@samsung.com \
--to=jonghwa3.lee@samsung.com \
--cc=kernel-janitors@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).