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

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH] free_irq(): Actually handle DEBUG_SHIRQ
  - From: "Maciej W. Rozycki" <[email protected]>

Prev by Date: [PATCH 4/5][AFS] Use macro instead of explicit check for mandatory locks
Next by Date: Re: [PATCH] Hookup group-scheduler with task container infrastructure
Previous by thread: [PATCH] free_irq(): Actually handle DEBUG_SHIRQ
Next by thread: [PATCH 1/5] Use existing macros for distinguishing mandatory locks
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]