---

yaml --- r: 32678 b: refs/heads/master c: 27b437c h: refs/heads/master v: v3
git-mirror · Jul 14, 2006 · b15ad0e · b15ad0e
1 parent 4a9a6fc
commit b15ad0e
Show file tree

Hide file tree

Showing 115 changed files with 409 additions and 4,554 deletions.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 52393ccc0a53c130f31fbbdb8b40b2aadb55ee72
+refs/heads/master: 27b437c8b7d519aac70a0254c2e04c29eff565a2
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