From: linux@solonet.org.ua (Denis Kuzmenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 resend] Fix compilation error when CONFIG_CPU_FREQ_S3C24XX_DEBUGFS selected.
Date: Wed, 21 Dec 2011 21:49:38 +0200 [thread overview]
Message-ID: <4EF23852.1050304@solonet.org.ua> (raw)
In-Reply-To: <064501ccbfae$cf1e5cb0$6d5b1610$%kim@samsung.com>
On 12/21/2011 09:04 AM, Kukjin Kim wrote:
> Denis Kuzmenko wrote:
>>
>> Fix compilation error when CONFIG_CPU_FREQ_S3C24XX_DEBUGFS selected.
>>
>> Signed-off-by: Denis Kuzmenko <linux@solonet.org.ua>
>> ---
>>
>> Patch is against 3.2-rc4.
>> CONFIG_S3C2410_IOTIMING is not selected for MACH_MINI2440. Because of this
>> the
>> file s3c2410-iotiming.c is not ever compiled and enabling
>> CONFIG_CPU_FREQ_S3C24XX_DEBUGFS option caused undefined reference to
>> function
>> s3c2410_iotiming_debugfs defined in that file. s3c2410_iotiming_debugfs
>> defined
>> as NULL for this case.
>>
> Hi Denis,
>
> Well, there is no error when CONFIG_CPU_FREQ_S3C24XX_DEBUGFS selected in my
> case and s3c2410-iotiming.c is built...when is it happened? I just selected
> every regarding configuration in kernel menuconfig...
Please, try attached config (it's still failing in v3.2-rc6).
--
Best regards, Denis Kuzmenko.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: .config
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20111221/e70a99b9/attachment-0001.ksh>
next prev parent reply other threads:[~2011-12-21 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 21:06 [PATCHv2 resend] Fix compilation error when CONFIG_CPU_FREQ_S3C24XX_DEBUGFS selected Denis Kuzmenko
2011-12-21 7:04 ` Kukjin Kim
2011-12-21 19:49 ` Denis Kuzmenko [this message]
2011-12-21 22:04 ` Kukjin Kim
2011-12-22 0:40 ` Denis Kuzmenko
2011-12-22 1:44 ` Kukjin Kim
2011-12-28 7:59 ` Kukjin Kim
2011-12-28 21:02 ` Denis Kuzmenko
2011-12-29 3:44 ` 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=4EF23852.1050304@solonet.org.ua \
--to=linux@solonet.org.ua \
--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).