From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] cpufreq: exynos: Fix build error of no type of module_init
Date: Wed, 22 Jan 2014 17:10:07 +0100 [thread overview]
Message-ID: <1390407007.18340.13.camel@AMDC1943> (raw)
In-Reply-To: <52DFE7D9.5050001@windriver.com>
On Wed, 2014-01-22 at 10:46 -0500, Paul Gortmaker wrote:
> On 14-01-22 10:37 AM, Krzysztof Kozlowski wrote:
> >
> >>
> >> Hi,
> >>
> >> A little more explanation from my side: the build error actually happens
> >> only on next/master, not Linus' tree.
> >>
> >> Mentioned commit which changes the driver to platform driver is in
> >> mainline since 3.12-rc2 so it seems this is not the cause of the build
> >> error. I think I need to find first the real cause of this build error.
> >>
> >> Best regards,
> >> Krzysztof
> >
> > After bisecting, the real commit for build error is:
> > caa7dcde7c424cdc81698a6e4e48072eb67ec67e
> > module: relocate module_init from init.h to module.h
>
> Yep, even though I fixed a crap-tonne of implicit includes, and
> built all the arm configs, some were bound to sneak through.
>
> I'll push a fix shortly to the init cleanup queue:
>
> http://git.kernel.org/cgit/linux/kernel/git/paulg/init.git/
>
> so it will be fine for the next linux-next tree.
Thanks, the same issue applies to drivers/cpufreq/exynos-cpufreq.c.
Best regards,
Krzysztof
prev parent reply other threads:[~2014-01-22 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 14:21 [PATCH RESEND] cpufreq: exynos: Fix build error of no type of module_init Krzysztof Kozlowski
2014-01-22 14:42 ` Viresh Kumar
2014-01-22 14:59 ` Krzysztof Kozlowski
2014-01-22 15:37 ` Krzysztof Kozlowski
2014-01-22 15:46 ` Paul Gortmaker
2014-01-22 16:10 ` Krzysztof Kozlowski [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=1390407007.18340.13.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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).