[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-id: <029101ccc5dc$1c718360$55548a20$%kim@samsung.com>
Date: Thu, 29 Dec 2011 12:44:04 +0900
From: Kukjin Kim <kgene.kim@...sung.com>
To: 'Denis Kuzmenko' <linux@...onet.org.ua>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org,
'Russell King' <linux@....linux.org.uk>,
'Ben Dooks' <ben-linux@...ff.org>
Subject: RE: [PATCHv2 resend] Fix compilation error when
CONFIG_CPU_FREQ_S3C24XX_DEBUGFS selected.
Denis Kuzmenko wrote:
>
> Hi Kukjin,
>
Hi Denis,
> Your patch applies (note that it looks like your email-client have
Yeah, if over 76 columns, my e-mail client changes its line so maybe
happened wrapped long lines.
> wrapped long lines thus broke the path) and works OK. Looks good to me.
> See some additional comments below.
>
> On 12/28/2011 09:59 AM, Kukjin Kim wrote:
> > Denis Kuzmenko wrote:
> (snip)
> >> + depends on CPU_FREQ_S3C24XX && (S3C2410_IOTIMING ||
> >> S3C2412_IOTIMING)
> >
> > As you know, CONFIG_CPU_FREQ_S3C24XX_IODEBUG is for enabling of
> > s3c_freq_iodbg() and there is no problem when
> CONFIG_S3C241{0,2}_IOTIMING is
> > not selected, even though s3c_freq_iodbg() is used only at
> > s3c2410-iotiming.c now. So this is not necessary to fix the problem you
> > said.
>
> I'm OK with this approach, however I don't see any future use of
> s3c_freq_iodbg() without s3c2410-iotiming.c. But it's not anyway
> critical so please pick any variant which you like.
>
Yes. I think we need to sort out the CPUFREQ on S3C24XX next time :)
(snip)
> (snip)
> > So how about at below?
> > If you're ok, will send before v3.2.
>
> So, as already said, I have no objections.
> And thank you for review.
>
Thanks and Happy New Year!
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@...sung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists