---

yaml --- r: 32689 b: refs/heads/master c: cc08632 h: refs/heads/master i: 32687: 2fb3057 v: v3
git-mirror · Jul 15, 2006 · a19e36c · a19e36c
1 parent 6cf2cd4
commit a19e36c
Show file tree

Hide file tree

Showing 124 changed files with 395 additions and 4,617 deletions.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 5694ca9f46202c50df525472abb6d8c1dee4f8eb
+refs/heads/master: cc08632f8f26d479500f8107c84e206770cb901c
diff --git a/trunk/Documentation/DMA-mapping.txt b/trunk/Documentation/DMA-mapping.txt
@@ -698,12 +698,12 @@ these interfaces.  Remember that, as defined, consistent mappings are
 always going to be SAC addressable.
 
 The first thing your driver needs to do is query the PCI platform
-layer if it is capable of handling your devices DAC addressing
-capabilities:
+layer with your devices DAC addressing capabilities:
 
-	int pci_dac_dma_supported(struct pci_dev *hwdev, u64 mask);
+	int pci_dac_set_dma_mask(struct pci_dev *pdev, u64 mask);
 
-You may not use the following interfaces if this routine fails.
+This routine behaves identically to pci_set_dma_mask.  You may not
+use the following interfaces if this routine fails.
 
 Next, DMA addresses using this API are kept track of using the
 dma64_addr_t type.  It is guaranteed to be big enough to hold any

diff --git a/trunk/Documentation/accounting/delay-accounting.txt b/trunk/Documentation/accounting/delay-accounting.txt