On Fri, Mar 09, 2012 at 10:51:27AM -0600, Rob Herring wrote: > On 03/08/2012 09:13 PM, Benjamin Herrenschmidt wrote: > > On Fri, 2012-03-09 at 00:39 +0000, Russell King wrote: > >> On Fri, Mar 09, 2012 at 10:35:46AM +1100, Benjamin Herrenschmidt wrote: > >>> Actually, I didn't keep MAY_HAVE_SPARSE_IRQ, I kept HAVE_SPARSE_IRQ. If > >>> I remove it, then I get Kconfig warnings: > >>> > >>> warning: (PPC) selects SPARSE_IRQ which has unmet direct dependencies > >>> (HAVE_GENERIC_HARDIRQS && HAVE_SPARSE_IRQ) > >> > >> Do you have commit 2ed86b16eabe4efbf80cc725a8cbb5310746a2fc ? > > > > Nope, Grant patch didn't mention a dependency. > > My opinion is that SPARSE_IRQ shouldn't be user visible option, and the > simple solution was to just make it hidden. It wasn't clear if this was > desired or not for other arches at the time. There is a mixture of > settings in powerpc defconfigs. SuperH selects it for 32-bit and leaves > it user selectable for 64-bit. > > I'm happy to revert adding MAY_HAVE_SPARSE_IRQ and just make SPARSE_IRQ > a hidden option. It really just needs the okay from SuperH folks. > We basically want it always-enabled for 32-bit and it doesn't matter much about 64-bit. In the future I'll probably fix up the 64-bit stuff to use it too and then we'll just leave it on all the time, but it's not such a big deal if it's not visible for enabling on 64-bit at the moment given that it's probably broken there at the moment. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
