Re: [PATCH] free_irq(): Actually handle DEBUG_SHIRQ

From: David Woodhouse
Date: Wed Sep 12 2007 - 07:30:09 EST

Next message: Srivatsa Vaddagiri: "Re: [PATCH] Hookup group-scheduler with task container infrastructure"
Previous message: Pavel Emelyanov: "[PATCH 4/5][AFS] Use macro instead of explicit check for mandatorylocks"
In reply to: Maciej W. Rozycki: "[PATCH] free_irq(): Actually handle DEBUG_SHIRQ"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, 2007-09-12 at 12:17 +0100, Maciej W. Rozycki wrote:
> Code used for DEBUG_SHIRQ in free_irq() is unreachable -- the for()
> loop within never terminates otherwise than by return. This is an
> obvious fix.

Yeah... except that it enables new debugging code which (due to my
stupidity) wasn't enabled before. A fix for this is already in the -mm
tree, to be merged (along with a corresponding lockdep-related fix)
after 2.6.23 release.

--
dwmw2

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Srivatsa Vaddagiri: "Re: [PATCH] Hookup group-scheduler with task container infrastructure"
Previous message: Pavel Emelyanov: "[PATCH 4/5][AFS] Use macro instead of explicit check for mandatorylocks"
In reply to: Maciej W. Rozycki: "[PATCH] free_irq(): Actually handle DEBUG_SHIRQ"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]