|| ||Jeff Garzik <email@example.com>|
|| ||David Howells <firstname.lastname@example.org>, email@example.com,
|| ||[PATCH, RAW] IRQ: Maintain irq number globally rather than passing
to IRQ handlers|
|| ||Fri, 06 Oct 2006 11:18:04 -0400|
|| ||Ingo Molnar <firstname.lastname@example.org>, Alan Cox <email@example.com>,
Andrew Morton <firstname.lastname@example.org>,
Thomas Gleixner <email@example.com>, firstname.lastname@example.org,
Dmitry Torokhov <email@example.com>, Greg KH <firstname.lastname@example.org>,
David Brownell <email@example.com>,
Alan Stern <firstname.lastname@example.org>|
Here is the raw, un-split-up first pass of the irq argument removal
patch (500K): http://gtf.org/garzik/misc/patch.irq-remove
* raw first pass, DO NOT APPLY.
* this was useful work: it turned up several minor bugs
* Do we mark irq handlers FASTCALL? If not, we probably can now.
* I also turned up a few obvious places that dhowells missed in his
pt_regs patch, inevitably in non-x86 arches that probably were not built.
* I need to fix up ~10 or so drivers that called their interrupt
handlers directly, then used a 'irq == 0' test to determine whether the
interrupt handler was called internally, or by the system.
* not sure yet if I want to mark the parport "irq handler" functions as
* Hopefully I will have this polished by the end of the day.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/