linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	linux-kernel@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 10/10] mach-ux500: update and move cpufreq driver
Date: Tue, 10 May 2011 01:59:26 -0400	[thread overview]
Message-ID: <20110510055926.GA2747@redhat.com> (raw)
In-Reply-To: <201105061522.33179.arnd@arndb.de>

On Fri, May 06, 2011 at 03:22:33PM +0200, Arnd Bergmann wrote:
 > On Friday 06 May 2011, Linus Walleij wrote:
 > > 
 > > From: Linus Walleij <linus.walleij@linaro.org>
 > > 
 > > This updates the ux500 cpufreq driver to the new interface from the
 > > updated DB8500 PRCMU driver and moves it to drivers/cpufreq as
 > > discussed with Dave Jones.
 > > 
 > > The Makefile change in drivers/cpufreq will collide with Daves commit
 > > moving cpufreq drivers into drivers/cpufreq/*, this needs to be fixed up
 > > in next or the merge window since this driver depend deeply on other
 > > changes in this patchset and GPIO consolidation.
 > > 
 > > Cc: Arnd Bergmann <arnd@arndb.de>
 > > Cc: Dave Jones <davej@redhat.com>
 > > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
 > 
 > Looks good for all I can tell, but please split this into two patches,
 > one for the conversion to the new interface and one for the actual
 > move. That would make it possible to review the changes you did.

Haven't had chance to really read much patches the last few days
(travelling until the 16th).  Due to the patch collisions we'll keep
seeing on kconfig/Makefiles, should these go via the cpufreq tree,
or do people want to still push them through their respective arch trees ?

When I'm back, I'm happy to take them if that's the decision.

	Dave


  reply	other threads:[~2011-05-10  5:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 13:06 [PATCH 10/10] mach-ux500: update and move cpufreq driver Linus Walleij
2011-05-06 13:22 ` Arnd Bergmann
2011-05-10  5:59   ` Dave Jones [this message]
2011-05-10 23:54     ` Linus Walleij
2011-05-16  9:02     ` Linus Walleij
2011-05-17 21:12       ` Dave Jones
2011-05-17 23:07         ` Nicolas Pitre
2011-05-18  5:21           ` Linus Walleij
2011-05-18  5:18         ` Linus Walleij

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=20110510055926.GA2747@redhat.com \
    --to=davej@redhat.com \
    --cc=arnd@arndb.de \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).