cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Kyungmin Park <kmpark@infradead.org>,
	linux-arm-kernel@lists.infradead.org,
	Dave Jones <davej@redhat.com>, Kukjin Kim <kgene.kim@samsung.com>,
	Ben Dooks <ben-linux@fluff.org>,
	cpufreq@vger.kernel.org
Subject: Re: [PATCH 1/5] CPUFREQ/S3C64xx: Move S3C64xx CPUfreq driver into drivers/cpufreq
Date: Wed, 01 Jun 2011 13:00:38 -0700	[thread overview]
Message-ID: <4DE69A66.9090002@samsung.com> (raw)
In-Reply-To: <20110601095811.GB13591@opensource.wolfsonmicro.com>

On 06/01/11 02:58, Mark Brown wrote:
> On Wed, Jun 01, 2011 at 06:55:05PM +0900, Kyungmin Park wrote:
>
>> Instead of samsung tree, it should be handled at cpufreq tree.
>> CCed the cpufreq maintainer.
>
> Well, it's a something for both really as both trees are updated.  I
> sent the orginal copy of this patch to both places but both sets of
> maintainers just ignored it (I've never seen any response from the
> cpufreq maintainers on this driver ever since I originally submitted
> it).
>
Hi Mark,

Sorry for late response.
Basically, you're moving is great to me and will review in 1 day.

As I remember, 800Mhz support on S3C6410 is ok and replied about that.
Then isn't there any progress in my side?...I'm outside of my office.

> At the minute I'm mostly just trying to get some of the backlog of
> S3C64xx patches I'm accumilating out of my queue :(

Dave, I'd like to talk about moving Samsung cpufreq drivers. I sent
about Kconfig.arm. If you're ok, will submit remained one to move
all of Samsung cpufreq drivers. And if possible would be better to me,
if someone(you or me) could make some branch to merge into both.

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

  parent reply	other threads:[~2011-06-01 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110601094313.GA23122@opensource.wolfsonmicro.com>
     [not found] ` <1306921493-30911-1-git-send-email-broonie@opensource.wolfsonmicro.com>
2011-06-01  9:55   ` [PATCH 1/5] CPUFREQ/S3C64xx: Move S3C64xx CPUfreq driver into drivers/cpufreq Kyungmin Park
2011-06-01  9:58     ` Mark Brown
2011-06-01 16:45       ` Dave Jones
2011-06-07  0:59         ` Dave Jones
2011-06-01 20:00       ` Kukjin Kim [this message]
2011-06-01 20:01         ` Mark Brown
2011-06-01 20:30           ` 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=4DE69A66.9090002@samsung.com \
    --to=kgene.kim@samsung.com \
    --cc=ben-linux@fluff.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=kmpark@infradead.org \
    --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