On Thu, 7 Jul 2005, Linus Torvalds wrote: > Yes. Except that if hwif is NULL, we'll have other oopses since we access > that in other places. > > Why _is_ hwif NULL anyway? That's another, unrelated thing, and should > probably have a separate check and an early return. I was wondering about that one as well. Andi brought it up. - 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/
- Follow-Ups:
- References:
- [PATCH] Fix crash on boot in kmalloc_node IDE changes
- From: Andi Kleen <[email protected]>
- [another PATCH] Fix crash on boot in kmalloc_node IDE changes
- From: Christoph Lameter <[email protected]>
- Re: [another PATCH] Fix crash on boot in kmalloc_node IDE changes
- From: Linus Torvalds <[email protected]>
- Re: [another PATCH] Fix crash on boot in kmalloc_node IDE changes
- From: Christoph Lameter <[email protected]>
- Re: [another PATCH] Fix crash on boot in kmalloc_node IDE changes
- From: Linus Torvalds <[email protected]>
- [PATCH] Fix crash on boot in kmalloc_node IDE changes
- Prev by Date: Re: [Hdaps-devel] RE: Head parking (was: IBM HDAPS things are looking up)
- Next by Date: Unable to handle kernel paging request at virtual address ffffe000 - in linux-2.6.12.2
- Previous by thread: Re: [another PATCH] Fix crash on boot in kmalloc_node IDE changes
- Next by thread: Re: [another PATCH] Fix crash on boot in kmalloc_node IDE changes
- Index(es):