From: Sudeep Dutt <sudeep.dutt@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Siva Yerramreddy <yshivakrishna@gmail.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
Nikhil Rao <nikhil.rao@intel.com>,
Sudeep Dutt <sudeep.dutt@intel.com>,
Paul Bolle <pebolle@tiscali.nl>,
Himangi Saraogi <himangi774@gmail.com>,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org
Subject: [PATCH char-misc-next 2/2] dma: Fix MIC X100 DMA Driver Kconfig option
Date: Mon, 14 Jul 2014 14:23:52 -0700 [thread overview]
Message-ID: <2eadff30dc5e9642b82f523c0398bf20109dd622.1405370827.git.sudeep.dutt@intel.com> (raw)
In-Reply-To: <cover.1405370827.git.sudeep.dutt@intel.com>
In-Reply-To: <cover.1405370827.git.sudeep.dutt@intel.com>
Select DMA_ENGINE instead of DMAENGINE and delete the default
line as the default is 'n' anyways.
Link: https://lkml.org/lkml/2014/7/14/90
Reported-by: Paul Bolle <pebolle@tiscali.nl>
Signed-off-by: Sudeep Dutt <sudeep.dutt@intel.com>
---
drivers/dma/Kconfig | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
index 7c8b8c4..8f6afbf 100644
--- a/drivers/dma/Kconfig
+++ b/drivers/dma/Kconfig
@@ -36,8 +36,7 @@ comment "DMA Devices"
config INTEL_MIC_X100_DMA
tristate "Intel MIC X100 DMA Driver"
depends on 64BIT && X86 && INTEL_MIC_BUS
- select DMAENGINE
- default N
+ select DMA_ENGINE
help
This enables DMA support for the Intel Many Integrated Core
(MIC) family of PCIe form factor coprocessor X100 devices that
--
1.8.2.1
next prev parent reply other threads:[~2014-07-14 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 21:23 [PATCH char-misc-next 0/2] Fix minor issues reported in MIC drivers Sudeep Dutt
2014-07-14 21:23 ` [PATCH char-misc-next 1/2] misc: mic: Introduce the managed version of ioremap Sudeep Dutt
2014-07-14 21:23 ` Sudeep Dutt [this message]
2014-07-14 21:30 ` [PATCH char-misc-next 2/2] dma: Fix MIC X100 DMA Driver Kconfig option Paul Bolle
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=2eadff30dc5e9642b82f523c0398bf20109dd622.1405370827.git.sudeep.dutt@intel.com \
--to=sudeep.dutt@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=himangi774@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=pebolle@tiscali.nl \
--cc=yshivakrishna@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).