[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTim0uKnjhKdVookDY0LPfaoQFy_TRQ@mail.gmail.com>
Date: Wed, 11 May 2011 01:54:10 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Dave Jones <davej@...hat.com>, Arnd Bergmann <arnd@...db.de>,
Linus Walleij <linus.walleij@...ricsson.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
linux-kernel@...r.kernel.org, Lee Jones <lee.jones@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH 10/10] mach-ux500: update and move cpufreq driver
2011/5/10 Dave Jones <davej@...hat.com>:
> 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 ?
In this specific case it will likely have to be through my tree, since I'm
not just messing with the cpufreq driver but also the thing it is using
for communication proxy, i.e. the PRCMU MFD driver.
I'm mainly after seeing if it's in shape to be pushed into drivers/cpufreq/*
and then I will be rebasing and requesting Linus (Torvalds) to pull this
after your cpufreq changes are gone in first.
So right now I'm looking for ACKs.
Thanks,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists