On Sun, 12 Aug 2007, Andi Kleen wrote: > > Can you double check? I have a hard time believing it. Andi, read the code. The old code was fine. Your patch was the culprit. Linus - 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] Fix triplefault on x86-64 bootup
- From: Petr Vandrovec <[email protected]>
- Please remove ab144f5ec64c42218a555ec1dbde6b60cf2982d6 was Re: [discuss] [PATCH] Fix triplefault on x86-64 bootup
- From: Andi Kleen <[email protected]>
- Re: Please remove ab144f5ec64c42218a555ec1dbde6b60cf2982d6 was Re: [discuss] [PATCH] Fix triplefault on x86-64 bootup
- From: Petr Vandrovec <[email protected]>
- Re: Please remove ab144f5ec64c42218a555ec1dbde6b60cf2982d6 was Re: [discuss] [PATCH] Fix triplefault on x86-64 bootup
- From: Andi Kleen <[email protected]>
- [PATCH] Fix triplefault on x86-64 bootup
- Prev by Date: Re: [PATCH] Fix triplefault on x86-64 bootup
- Next by Date: Re: [PATCH] make atomic_t volatile on all architectures
- Previous by thread: Re: Please remove ab144f5ec64c42218a555ec1dbde6b60cf2982d6 was Re: [discuss] [PATCH] Fix triplefault on x86-64 bootup
- Next by thread: Re: [PATCH] Fix triplefault on x86-64 bootup
- Index(es):
 |