From: viresh kumar <viresh.kumar@st.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] ata: PATA_ARASAN_CF depends on DMADEVICES
Date: Tue, 24 May 2011 09:08:50 +0530 [thread overview]
Message-ID: <4DDB284A.6040603@st.com> (raw)
In-Reply-To: <4DDA89A2.8010604@oracle.com>
On 05/23/2011 09:51 PM, Randy Dunlap wrote:
>>> >> config PATA_ARASAN_CF
>>> >> tristate "ARASAN CompactFlash PATA Controller Support"
>>> >> + depends on DMADEVICES
>>> >> select DMA_ENGINE
>> >
>> > Randy,
>> >
>> > I think we can also remove this "select DMA_ENGINE" line.
> In that case, the newly added "depends on" line is not needed either,
> since the "select DMA_ENGINE" is what causes the kconfig warning message.
>
Some sort of dependency must be present as PATA_ARASAN is using DMAENGINE
routines and it will not compile unless DMA_ENGINE is enabled.
So, depends on DMADEVICES will solve all these issues.
--
viresh
next prev parent reply other threads:[~2011-05-24 3:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 6:55 linux-next: Tree for May 20 Stephen Rothwell
2011-05-20 17:54 ` linux-next: Tree for May 20 (iwlwifi) Randy Dunlap
2011-05-20 18:35 ` wwguy
2011-05-23 0:32 ` [PATCH -next] ata: PATA_ARASAN_CF depends on DMADEVICES Randy Dunlap
2011-05-23 3:35 ` viresh kumar
2011-05-23 16:21 ` Randy Dunlap
2011-05-24 3:38 ` viresh kumar [this message]
2011-05-23 0:34 ` [PATCH -next] media: fix kconfig dependency warning for VIDEO_TIMBERDALE Randy Dunlap
2011-05-23 0:38 ` [PATCH -next] firmware: fix GOOGLE_SMI kconfig dependency warning Randy Dunlap
[not found] ` <BANLkTi=T4JsDZ7EX18AHcwG8nd50FzHGtg@mail.gmail.com>
2011-05-23 15:15 ` Randy Dunlap
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=4DDB284A.6040603@st.com \
--to=viresh.kumar@st.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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.