From: Dave Jones <davej@redhat.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: Jaecheol Lee <jc.lee@samsung.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 RE-SEND] [CPUFREQ] EXYNOS5250: Add support cpufreq for EXYNOS5250
Date: Wed, 14 Mar 2012 14:40:53 -0400 [thread overview]
Message-ID: <20120314184053.GC3803@redhat.com> (raw)
In-Reply-To: <4F60E25C.9060005@samsung.com>
On Wed, Mar 14, 2012 at 11:24:28AM -0700, Kukjin Kim wrote:
> 2012-03-14 오전 10:57, Dave Jones 쓴 글:
> > On Wed, Mar 14, 2012 at 10:31:42AM -0700, Kukjin Kim wrote:
> > > Kukjin Kim wrote:
> > > > From: Jaecheol Lee<jc.lee@samsung.com>
> > > >
> > > > This patch adds support cpufreq for EXYNOS5250 SoC. Basically,
> > > > the exynos-cpufreq.c is used commonly and exynos5250-cpufreq.c
> > > > is used for EXYNOS5250(two Cortex-A15 cores) SoC.
> > > >
> > > > Signed-off-by: Jaecheol Lee<jc.lee@samsung.com>
> > > > Signed-off-by: Kukjin Kim<kgene.kim@samsung.com>
> > >
> > > Hi again Dave :)
> > >
> > > Please pick up this patch for v3.4.
> > > If any problems, please kindly let us know.
> >
> > this, and the other patch doesn't apply against current cpufreq.git
> >
> Oops, maybe you applied this first. Pleae try again EXYNOS4X12 first
> then, this. I applied on top of cpufreq/next and there was no complain.
>
> If any problems, please kindly let me know.
Applied and pushed. thanks!
Dave
WARNING: multiple messages have this Message-ID (diff)
From: davej@redhat.com (Dave Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 RE-SEND] [CPUFREQ] EXYNOS5250: Add support cpufreq for EXYNOS5250
Date: Wed, 14 Mar 2012 14:40:53 -0400 [thread overview]
Message-ID: <20120314184053.GC3803@redhat.com> (raw)
In-Reply-To: <4F60E25C.9060005@samsung.com>
On Wed, Mar 14, 2012 at 11:24:28AM -0700, Kukjin Kim wrote:
> 2012-03-14 ?? 10:57, Dave Jones ? ?:
> > On Wed, Mar 14, 2012 at 10:31:42AM -0700, Kukjin Kim wrote:
> > > Kukjin Kim wrote:
> > > > From: Jaecheol Lee<jc.lee@samsung.com>
> > > >
> > > > This patch adds support cpufreq for EXYNOS5250 SoC. Basically,
> > > > the exynos-cpufreq.c is used commonly and exynos5250-cpufreq.c
> > > > is used for EXYNOS5250(two Cortex-A15 cores) SoC.
> > > >
> > > > Signed-off-by: Jaecheol Lee<jc.lee@samsung.com>
> > > > Signed-off-by: Kukjin Kim<kgene.kim@samsung.com>
> > >
> > > Hi again Dave :)
> > >
> > > Please pick up this patch for v3.4.
> > > If any problems, please kindly let us know.
> >
> > this, and the other patch doesn't apply against current cpufreq.git
> >
> Oops, maybe you applied this first. Pleae try again EXYNOS4X12 first
> then, this. I applied on top of cpufreq/next and there was no complain.
>
> If any problems, please kindly let me know.
Applied and pushed. thanks!
Dave
next prev parent reply other threads:[~2012-03-14 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 11:00 [PATCH v2 RE-SEND] [CPUFREQ] EXYNOS5250: Add support cpufreq for EXYNOS5250 Kukjin Kim
2012-03-10 11:00 ` Kukjin Kim
2012-03-14 17:31 ` Kukjin Kim
2012-03-14 17:31 ` Kukjin Kim
2012-03-14 17:57 ` Dave Jones
2012-03-14 17:57 ` Dave Jones
2012-03-14 18:24 ` Kukjin Kim
2012-03-14 18:24 ` Kukjin Kim
2012-03-14 18:40 ` Dave Jones [this message]
2012-03-14 18:40 ` Dave Jones
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=20120314184053.GC3803@redhat.com \
--to=davej@redhat.com \
--cc=jc.lee@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.