From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Denis Kuzmenko'" <linux@solonet.org.ua>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
"'Russell King'" <linux@arm.linux.org.uk>,
"'Ben Dooks'" <ben-linux@fluff.org>
Subject: RE: [PATCHv2 resend] Fix compilation error when CONFIG_CPU_FREQ_S3C24XX_DEBUGFS selected.
Date: Thu, 22 Dec 2011 10:44:04 +0900 [thread overview]
Message-ID: <073601ccc04b$2fcff5e0$8f6fe1a0$%kim@samsung.com> (raw)
In-Reply-To: <4EF27C76.3020805@solonet.org.ua>
Denis Kuzmenko wrote:
>
> On 12/22/2011 12:04 AM, Kukjin Kim wrote:
> > Denis Kuzmenko wrote:
> >>
> >> 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).
> >>
> > Hi Denis,
> >
> > Yes, when s3c2410 stuff is not selected, it happened.
> > Look at me soon and thanks.
> Hi, Kukjin,
>
> Sorry, can you please explain as I can't understand. Especially second
> sentence.
>
Oops, mis-typing. Let me look at that with your patch :)
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2011-12-22 1:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 21:06 Denis Kuzmenko
2011-12-21 7:04 ` Kukjin Kim
2011-12-21 19:49 ` Denis Kuzmenko
2011-12-21 22:04 ` Kukjin Kim
2011-12-22 0:40 ` Denis Kuzmenko
2011-12-22 1:44 ` Kukjin Kim [this message]
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='073601ccc04b$2fcff5e0$8f6fe1a0$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@solonet.org.ua \
/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
all inboxes | Powered by JetHome®