[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160329113856.GB6745@arm.com>
Date: Tue, 29 Mar 2016 12:38:57 +0100
From: Will Deacon <will.deacon@....com>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
Cc: linux-kernel@...r.kernel.org,
Florian Fainelli <f.fainelli@...il.com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Arnd Bergmann <arnd@...db.de>,
Wolfram Sang <wsa@...-dreams.de>,
Sascha Hauer <s.hauer@...gutronix.de>,
Shawn Guo <shawn.guo@...aro.org>,
Kevin Hilman <khilman@...aro.org>,
Pawel Moll <pawel.moll@....com>,
Gregory Fong <gregory.0xf0@...il.com>,
Olof Johansson <olof@...om.net>,
Simon Horman <horms+renesas@...ge.net.au>,
Brian Norris <computersforpeace@...il.com>,
Alison Chaiken <alison_chaiken@...tor.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/4] drivers/bus: remove unused modular code from
non-modular drivers
On Sun, Mar 27, 2016 at 05:10:54PM -0400, Paul Gortmaker wrote:
> The drivers/bus doesn't have a strict maintainer entry, but since
> all the changes here are for ARM platforms, I'm Cc'ing arm-kernel
> and hoping it makes sense to vector these few changes through the
> arm-soc. [Olof, Will, Arnd? Seems you guys handle most of it...]
I plan to move the parts that are simply perf drivers under drivers/perf,
so that should remove some of the code from drivers/bus. There's a fiddly
part with the CCI, which has both perf code and bus initialisation code
that need prying apart.
Will
Powered by blists - more mailing lists