Commit:     6d4f5879b6f4da50bde94e1cae73755978ed048f
Parent:     e593f070b40887dc0415646a4c0720eb8630c722
Author:     Haavard Skinnemoen <[EMAIL PROTECTED]>
AuthorDate: Wed Nov 28 16:21:43 2007 -0800
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Thu Nov 29 09:24:53 2007 -0800

    dmaengine: correct invalid assumptions in the Kconfig text
    This patch corrects recently changed (and now invalid) Kconfig descriptions
    for the DMA engine framework:
     - Non-Intel(R) hardware also has DMA engines;
     - DMA is used for more than memcpy and RAID offloading.
    In fact, on most platforms memcpy and RAID aren't factors, and DMA
    exists so that peripherals can transfer data to/from memory while
    the CPU does other work.
    Signed-off-by: Haavard Skinnemoen <[EMAIL PROTECTED]>
    Signed-off-by: David Brownell <[EMAIL PROTECTED]>
    Signed-off-by: Dan Williams <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
 drivers/dma/Kconfig |    8 +++++---
 1 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
index 6a7d25f..c46b7c2 100644
--- a/drivers/dma/Kconfig
+++ b/drivers/dma/Kconfig
@@ -3,11 +3,13 @@
 menuconfig DMADEVICES
-       bool "DMA Offload Engine support"
+       bool "DMA Engine support"
        depends on (PCI && X86) || ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX
-         Intel(R) offload engines enable offloading memory copies in the
-         network stack and RAID operations in the MD driver.
+         DMA engines can do asynchronous data transfers without
+         involving the host CPU.  Currently, this framework can be
+         used to offload memory copies in the network stack and
+         RAID operations in the MD driver.
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to