Re: [PATCH 2/2] [TULIP] Check the return value from pci_set_mwi()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Matthew Wilcox <[email protected]>
Subject: Re: [PATCH 2/2] [TULIP] Check the return value from pci_set_mwi()
From: Jeff Garzik <[email protected]>
Date: Fri, 06 Oct 2006 15:15:15 -0400
Cc: Val Henson <[email protected]>, Greg Kroah-Hartman <[email protected]>, [email protected], [email protected], [email protected]
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]>
Sender: [email protected]
User-agent: Thunderbird 1.5.0.7 (X11/20060913)

Matthew Wilcox wrote:

Also, pci_set_mwi() will fail if the cache line
size is 0, so we don't need to check that ourselves any more.

NAK, not true on all arches. sparc64 at least presumes that thefirmware DTRT with cacheline size, which hurts us now given this tulip patch


	Jeff


-
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 2/2] [TULIP] Check the return value from pci_set_mwi()
  - From: Matthew Wilcox <[email protected]>

References:
- [PATCH 1/2] [PCI] Check that MWI bit really did get set
  - From: Matthew Wilcox <[email protected]>
- [PATCH 2/2] [TULIP] Check the return value from pci_set_mwi()
  - From: Matthew Wilcox <[email protected]>

Prev by Date: 2.6.19-rc1: Oops in probe_hwif
Next by Date: Re: [PATCH 1/2] [PCI] Check that MWI bit really did get set
Previous by thread: [PATCH 2/2] [TULIP] Check the return value from pci_set_mwi()
Next by thread: Re: [PATCH 2/2] [TULIP] Check the return value from pci_set_mwi()
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]

Powered by Linux