Basically we are going around in circles inventing new random hypothetical rule sets that may or may not fix the problem. You can do this for years, in fact we *have* been doing this for years. The detailed stuff I posted by digging over all the docs should be enough to figure out WTF is actually going on and fix the stuff properly. - 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:
- Re: [PATCH V3] VIA IRQ quirk behaviour change
- From: Daniel Drake <[email protected]>
- Re: [PATCH V3] VIA IRQ quirk behaviour change
- From: Jeff Garzik <[email protected]>
- Re: [PATCH V3] VIA IRQ quirk behaviour change
- References:
- [PATCH V3] VIA IRQ quirk behaviour change
- From: Daniel Drake <[email protected]>
- Re: [PATCH V3] VIA IRQ quirk behaviour change
- From: Alan Cox <[email protected]>
- Re: [PATCH V3] VIA IRQ quirk behaviour change
- From: Daniel Drake <[email protected]>
- Re: [PATCH V3] VIA IRQ quirk behaviour change
- From: Alan Cox <[email protected]>
- Re: [PATCH V3] VIA IRQ quirk behaviour change
- From: Daniel Drake <[email protected]>
- Re: [PATCH V3] VIA IRQ quirk behaviour change
- From: Alan Cox <[email protected]>
- Re: [PATCH V3] VIA IRQ quirk behaviour change
- From: Daniel Drake <[email protected]>
- [PATCH V3] VIA IRQ quirk behaviour change
- Prev by Date: Re: [PATCH 3/4] security: capabilities patch (version 0.4.4), part 3/4: introduce new capabilities
- Next by Date: [PATCH] force_quiescent_state: factor out duplicated code
- Previous by thread: Re: [PATCH V3] VIA IRQ quirk behaviour change
- Next by thread: Re: [PATCH V3] VIA IRQ quirk behaviour change
- Index(es):
 |