On Fri, Oct 19, 2007 at 03:54:43AM -0400, Jeff Garzik wrote: > > WARNING NOT FOR MERGE WARNING NOT FOR MERGE WARNING NOT FOR MERGE
then whats the point ? > > This posting is just to demonstrate something that I have been keeping > alive in the background. I have no urge to push it upstream anytime > soon. why not? --mgross > > The overwhelming majority of drivers do not ever bother with the 'irq' > argument that is passed to each driver's irq handler. > > Of the minority of drivers that do use the arg, the majority of those > have the irq number stored in their private-info structure somewhere. > > There are a tiny few -- a couple Mac drivers -- which do weird things > with that argument, but that's it. > > For the large sweeps through the tree, these patches are grouped into > "trivial" changes -- simply removing the unused irq arg -- or all other > changes. > > [IRQ ARG REMOVAL] core interrupt delivery infrastructure updates > [IRQ ARG REMOVAL] various non-trivial arch updates > [IRQ ARG REMOVAL] trivial arch updates > [IRQ ARG REMOVAL] non-trivial driver updates > [IRQ ARG REMOVAL] trivial net driver updates > [IRQ ARG REMOVAL] trivial sound driver updates > [IRQ ARG REMOVAL] trivial scsi driver updates > [IRQ ARG REMOVAL] trivial driver updates > [IRQ ARG REMOVAL] x86-64 build fixes, cleanups > > WARNING NOT FOR MERGE WARNING NOT FOR MERGE WARNING NOT FOR MERGE > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/