linux-kernel - Re: [PATCH 06/14] mfd: Initialise the DB8500 PRCMU driver at core

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201206121449.22978.arnd@arndb.de>
Date:	Tue, 12 Jun 2012 14:49:22 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	grant.likely@...retlab.ca, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, linus.walleij@...ricsson.com,
	Samuel Ortiz <sameo@...ux.intel.com>
Subject: Re: [PATCH 06/14] mfd: Initialise the DB8500 PRCMU driver at core_initcall time

On Tuesday 12 June 2012, Lee Jones wrote:
> But your suggestion above involves some heavy refactoring of how Device 
> Tree works. Meanwhile the ab8500 will not work as an IRQ controller 
> until we either complete the work or use the same solution as we did for 
> the Nomadik GPIO controller. I think for now at least we should continue 
> to work on enablement and leave the 'nice to have's until last. We are 
> doing nothing new here, just bringing the ab8500 IRQ controller into 
> line with the Nomadik one.

Right, I didn't say we should not take your patch, but we should be
aware that it's not the solution we want to use in the long run.

	Arnd
--
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/