From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] Remove pci_dac_set_dma_mask() from Documentation/DMA-mapping.txt
Date: Wed, 12 Jul 2006 09:47:16 +0200 [thread overview]
Message-ID: <200607120947.17034@bilbo.math.uni-mannheim.de> (raw)
In-Reply-To: <200607120942.23071@bilbo.math.uni-mannheim.de>
pci_dac_set_dma_mask() gives only a single match in the whole kernel tree
and that's in this doc file. The best candidate for replacement is
pci_dac_dma_supported().
Signed-off-by: Rolf Eike Beer <eike-kernel@sf-tec.de>
---
commit 609c9a2c7a61f6fab9cb8507bb01e8bb8fa9f183
tree 6fccc01d3ac08c9a4bcec67a7ff430aa368b68c2
parent 7471539cb5e9cdd7ca7e48a247e15797d0e53708
author Rolf Eike Beer <eike-kernel@sf-tec.de> Wed, 12 Jul 2006 09:36:05 +0200
committer Rolf Eike Beer <beer@siso-eb-i34d.silicon-software.de> Wed, 12 Jul 2006 09:36:05 +0200
Documentation/DMA-mapping.txt | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/DMA-mapping.txt b/Documentation/DMA-mapping.txt
index 7c71769..63392c9 100644
--- a/Documentation/DMA-mapping.txt
+++ b/Documentation/DMA-mapping.txt
@@ -698,12 +698,12 @@ these interfaces. Remember that, as def
always going to be SAC addressable.
The first thing your driver needs to do is query the PCI platform
-layer with your devices DAC addressing capabilities:
+layer if it is capable of handling your devices DAC addressing
+capabilities:
- int pci_dac_set_dma_mask(struct pci_dev *pdev, u64 mask);
+ int pci_dac_dma_supported(struct pci_dev *hwdev, u64 mask);
-This routine behaves identically to pci_set_dma_mask. You may not
-use the following interfaces if this routine fails.
+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
prev parent reply other threads:[~2006-07-12 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 7:42 [PATCH 0/2] Documentation improvements Rolf Eike Beer
2006-07-12 7:46 ` [PATCH 1/2] add function documentation for register_chrdev() Rolf Eike Beer
2006-07-12 15:53 ` Randy.Dunlap
2006-07-13 6:49 ` Rolf Eike Beer
2006-07-13 7:09 ` [PATCH 1/2 v2] " Rolf Eike Beer
2006-07-12 7:47 ` Rolf Eike Beer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200607120947.17034@bilbo.math.uni-mannheim.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox