From: Kukjin Kim <kgene.kim@samsung.com>
To: Dave Jones <davej@redhat.com>, Kukjin Kim <kgene.kim@samsung.com>,
Donggeun Kim <dg77.kim@samsung.com>,
cpufreq@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kyungmin.park@samsung.com,
myungjoo.ham@samsung.com, Ben Dooks <ben-linux@fluff.org>
Subject: Re: [PATCH] CPUFREQ/S5PV210, EXYNOS4: Add Kconfig options for S5PV210 and EXYNOS4 CPUfreq drivers
Date: Wed, 01 Jun 2011 13:28:18 -0700 [thread overview]
Message-ID: <4DE6A0E2.5040807@samsung.com> (raw)
In-Reply-To: <20110601195418.GA30806@redhat.com>
On 06/01/11 12:54, Dave Jones wrote:
> On Wed, Jun 01, 2011 at 12:48:14PM -0700, Kukjin Kim wrote:
>
> > Dave, could you please see below? If you're ok, will submit remained
> > others for Samsung cpufreq drivers.
>
> I'm ok with the principle of the patch, though it doesn't seem to include
> any driver movement, so just applying this will break the compile.
> (If it happens in another patch, they should really go together to
> not break bisecting)
>
Hi Dave,
OK, will submit others which include moving cpufreq driver soon.
If you don't mind I will make some branch to merge in both, my tree
and yours.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2011-06-01 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 6:07 [PATCH] CPUFREQ/S5PV210,EXYNOS4: Move S5PV210 and EXYNOS4 CPUfreq drivers into drivers/cpufreq Donggeun Kim
2011-05-27 8:04 ` [PATCH] CPUFREQ/S5PV210,EXYNOS4: Add Kconfig options for S5PV210 and EXYNOS4 CPUfreq drivers Donggeun Kim
2011-06-01 19:48 ` Kukjin Kim
2011-06-01 19:54 ` Dave Jones
2011-06-01 20:28 ` Kukjin Kim [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=4DE6A0E2.5040807@samsung.com \
--to=kgene.kim@samsung.com \
--cc=ben-linux@fluff.org \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=dg77.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
/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