All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI fixes for 2.6.0-test2
Date: Fri, 1 Aug 2003 12:32:07 -0700	[thread overview]
Message-ID: <10597663273174@kroah.com> (raw)
In-Reply-To: <10597663232556@kroah.com>

ChangeSet 1.1547.13.2, 2003/08/01 10:13:16-07:00, mitch@sfgoth.com

[PATCH] PCI: Trivial DMA-mapping.txt fix

As far as I can tell "pci_set_consistent()" doesn't exist - the docs probably
meant to say "pci_set_consistent_dma_mask()".


 Documentation/DMA-mapping.txt |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)


diff -Nru a/Documentation/DMA-mapping.txt b/Documentation/DMA-mapping.txt
--- a/Documentation/DMA-mapping.txt	Fri Aug  1 12:17:38 2003
+++ b/Documentation/DMA-mapping.txt	Fri Aug  1 12:17:38 2003
@@ -183,7 +183,7 @@
 pci_set_consistent_dma_mask() will always be able to set the same or a
 smaller mask as pci_set_dma_mask(). However for the rare case that a
 device driver only uses consistent allocations, one would have to
-check the return value from pci_set_consistent().
+check the return value from pci_set_consistent_dma_mask().
 
 If your 64-bit device is going to be an enormous consumer of DMA
 mappings, this can be problematic since the DMA mappings are a


  reply	other threads:[~2003-08-01 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 19:29 [BK PATCH] PCI fixes for 2.6.0-test2 Greg KH
2003-08-01 19:31 ` [PATCH] " Greg KH
2003-08-01 19:31   ` Greg KH
2003-08-01 19:31     ` Greg KH
2003-08-01 19:31       ` Greg KH
2003-08-01 19:32         ` Greg KH
2003-08-01 19:32           ` Greg KH
2003-08-01 19:32             ` Greg KH [this message]
2003-08-01 19:32               ` Greg KH

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=10597663273174@kroah.com \
    --to=greg@kroah.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.