Greg KH wrote: > No, that's not fair for those devices which do not have PCI-E and yet > have MSI (the original ones, that work just fine...) > > Again, no "whitelist" please, just quirks to fix problems with ones that > we know we have problems with, just like all other PCI quirks... > > thanks, > > greg k-h > Ok I will regenerate my patches to do so. Brice - 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:
- Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- From: Dave Olson <[email protected]>
- Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- From: Andi Kleen <[email protected]>
- Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- From: Greg KH <[email protected]>
- Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- From: Brice Goglin <[email protected]>
- Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- From: Greg KH <[email protected]>
- Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- Prev by Date: [PATCH] Fix 100% initramfs bloat in 2.6.17 versus 2.6.16
- Next by Date: Re: Linux 2.6.17: IRQ handler mismatch in serial code?
- Previous by thread: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- Next by thread: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilitiesKJ
- Index(es):