devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Viresh Kumar' <viresh.kumar@linaro.org>,
	'Jonghwan Choi' <jhbird.choi@samsung.com>,
	"'Rafael J. Wysocki'" <rjw@rjwysocki.net>
Cc: 'linux-samsung-soc' <linux-samsung-soc@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	cpufreq@vger.kernel.org
Subject: RE: [PATCH] cpufreq: exynos: Fix the compile error
Date: Fri, 16 May 2014 17:13:06 +0900	[thread overview]
Message-ID: <02f801cf70de$ad3eac10$07bc0430$@samsung.com> (raw)
In-Reply-To: <CAKohpokxDQ8w0-fJsyp+i3pLsq5Qyfyev-W8ZXXj8gbyP11pqQ@mail.gmail.com>

Viresh Kumar wrote:
> 
> And please use Rafael's email id from Maintainers..
> 
> On 16 May 2014 13:25, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > On 16 May 2014 13:20, Jonghwan Choi <jhbird.choi@samsung.com> wrote:
> >> Commit 7da83a80 ("ARM: EXYNOS: Migrate Exynos specific macros from
> >> plat to
> >> mach")
> >
> > Why do you have a line break here ?
> >
> >> which lands in samsung tree causes build breakage for cpufreq-exynos
> >> like
> >> following:
> >
> > Enter a blank line here..
> >
> >> drivers/cpufreq/exynos-cpufreq.c: In function 'exynos_cpufreq_probe':
> >> drivers/cpufreq/exynos-cpufreq.c:166:2: error: implicit declaration
> >> of function 'soc_is_exynos4210'
> >> [-Werror=implicit-function-declaration]
> >
> > Let these cross 80 columns, don't break them, its unreadable.
> >
> >> drivers/cpufreq/exynos-cpufreq.c:168:2: error: implicit declaration
> >> of function 'soc_is_exynos4212'
> >> [-Werror=implicit-function-declaration]
> >> drivers/cpufreq/exynos-cpufreq.c:168:2: error: implicit declaration
> >> of function 'soc_is_exynos4412'
> >> [-Werror=implicit-function-declaration]
> >> drivers/cpufreq/exynos-cpufreq.c:170:2: error: implicit declaration
> >> of function 'soc_is_exynos5250'
> >> [-Werror=implicit-function-declaration]
> >> cc1: some warnings being treated as errors
> >> make[2]: *** [drivers/cpufreq/exynos-cpufreq.o] Error 1
> >> make[2]: *** Waiting for unfinished jobs....
> >> drivers/cpufreq/exynos4x12-cpufreq.c: In function
> 'exynos4x12_set_clkdiv':
> >> drivers/cpufreq/exynos4x12-cpufreq.c:118:2: error: implicit
> >> declaration of function 'soc_is_exynos4212'
> >> [-Werror=implicit-function-declaration]
> >> cc1: some warnings being treated as errors
> >> make[2]: *** [drivers/cpufreq/exynos4x12-cpufreq.o] Error 1
> >> make[1]: *** [drivers/cpufreq] Error 2
> >
> > Two blank lines here.
> >
> >> This fixes above error with getting SoC information via DT instead of
> >> soc_is_exynosXXXX().
> >>
> >> Signed-off-by: Jonghwan Choi <jhbird.choi@samsung.com>
> >> ---
> >>  .../devicetree/bindings/cpufreq/cpufreq-exynos.txt |   18 ++++++++
> >>  drivers/cpufreq/Kconfig.arm                        |    4 +-
> >>  drivers/cpufreq/exynos-cpufreq.c                   |   47
> >> +++++++++++++++++---
> >>  drivers/cpufreq/exynos-cpufreq.h                   |    8 ++++
> >>  drivers/cpufreq/exynos4x12-cpufreq.c               |   11 ++---
> >>  5 files changed, 72 insertions(+), 16 deletions(-)
> >
> > I don't think anybody can call that a fix :)
> >
> > So what you have done is combined 'fix' with 'cleanups or improvements'.
> > That's surely wrong..
> >
Well, I think this is really _fix_ the build error, this adds support DT binding for exynos cpufreq stuff though. Because we cannot cover exynos cpufreq without this and you can see that on current -next tree.

> > Just give a simple fix for this breakage that will go in 3.15 and do
> > the DT stuff in another patch for 3.16..

In 3.15, it should be fine. Please check the -next tree and this should be sent to upstream for 3.16 not 3.15 via samsung tree with the patch (commit ID 7da83a80) which causes the build error.

Thanks,
Kukjin

  reply	other threads:[~2014-05-16  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16  7:50 [PATCH] cpufreq: exynos: Fix the compile error Jonghwan Choi
2014-05-16  7:55 ` Viresh Kumar
2014-05-16  7:56   ` Viresh Kumar
2014-05-16  8:13     ` Kukjin Kim [this message]
2014-05-16  8:25       ` Kukjin Kim

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='02f801cf70de$ad3eac10$07bc0430$@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jhbird.choi@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --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 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).