Re: [PATCH 1/2] [PCI] Check that MWI bit really did get set

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

To: Matthew Wilcox <[email protected]>
Subject: Re: [PATCH 1/2] [PCI] Check that MWI bit really did get set
From: Jeff Garzik <[email protected]>
Date: Fri, 06 Oct 2006 15:16:36 -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]>
Sender: [email protected]
User-agent: Thunderbird 1.5.0.7 (X11/20060913)

Matthew Wilcox wrote:

Since some devices may not implement the MWI bit, we should check that
the write did set it and return an error if it didn't.

Signed-off-by: Matthew Wilcox <[email protected]>

ACK, though (as it seems you are doing) you should audit pci_set_mwi()users to make sure behavior matches up with this implementation


	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/

References:
- [PATCH 1/2] [PCI] Check that MWI bit really did get set
  - From: Matthew Wilcox <[email protected]>

Prev by Date: Re: [PATCH 2/2] [TULIP] Check the return value from pci_set_mwi()
Next by Date: More info on section mismatches (was Re: [PATCH] [TULIP] Fix section mismatch in de2104x.c)
Previous by thread: Re: [PATCH 2/2] [TULIP] Check the return value from pci_set_mwi()
Next by thread: Re: [PATCH 1/2] [PCI] Check that MWI bit really did get set
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