---

yaml --- r: 32683 b: refs/heads/master c: d8573e2 h: refs/heads/master i: 32681: 0aeeeb5 32679: df66419 v: v3
git-mirror · Jul 15, 2006 · b3ff022 · b3ff022
1 parent 665f5e2
commit b3ff022
Show file tree

Hide file tree

Showing 120 changed files with 381 additions and 4,610 deletions.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 76aba64a6608fcaa02c715e93c572192f3621195
+refs/heads/master: d8573e20d5d6974305599dde42b5dd7583310ccf
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