From: Dave Jones <davej@redhat.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Kyungmin Park <kmpark@infradead.org>,
cpufreq@vger.kernel.org, Ben Dooks <ben-linux@fluff.org>,
Kukjin Kim <kgene.kim@samsung.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/5] CPUFREQ/S3C64xx: Move S3C64xx CPUfreq driver into drivers/cpufreq
Date: Mon, 6 Jun 2011 20:59:12 -0400 [thread overview]
Message-ID: <20110607005912.GB20918@redhat.com> (raw)
In-Reply-To: <20110601164510.GA21467@redhat.com>
On Wed, Jun 01, 2011 at 12:45:10PM -0400, Dave Jones wrote:
> On Wed, Jun 01, 2011 at 10:58:11AM +0100, 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).
>
> Sorry about that. It's actually in my 'to merge' mailbox, but I've been
> laggy at dealing with it recently. I'll try and clear the backlog in
> the next day or two.
Ok, I finally got around to sorting this out. It needed some small changes
to fix up rejects in drivers/cpufreq/Makefile, but they looked trivial enough
that I'm sure they're ok. But look them over anyway ?
I also applied the S5PV210/EXYNOS4210 patch which also needed the same fixing.
Both pushed out to cpufreq.next
Let me know if there's anything I've missed
thanks,
Dave
next prev parent reply other threads:[~2011-06-07 0:59 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 [this message]
2011-06-01 20:00 ` Kukjin Kim
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=20110607005912.GB20918@redhat.com \
--to=davej@redhat.com \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cpufreq@vger.kernel.org \
--cc=kgene.kim@samsung.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