From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: linux-input@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [RFC] mfd/ucb1400: don't depend on gpiolib
Date: Thu, 08 Jan 2009 13:37:15 +0100 [thread overview]
Message-ID: <4965F37B.6040304@linutronix.de> (raw)
In-Reply-To: <200901081325.53589.marek.vasut@gmail.com>
Marek Vasut wrote:
> On Thursday 08 of January 2009 12:06:12 Sebastian Andrzej Siewior wrote:
>> it didn't in the past and I can't see how it does.
>>
>> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>> ---
>> I use ucb1400 with its ts capabilities without *gpiolib* on a ppc system.
>>
>> drivers/mfd/Kconfig | 1 -
>> 1 files changed, 0 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
>> index 2572773..8bcd600 100644
>> --- a/drivers/mfd/Kconfig
>> +++ b/drivers/mfd/Kconfig
>> @@ -53,7 +53,6 @@ config HTC_PASIC3
>> config UCB1400_CORE
>> tristate "Philips UCB1400 Core driver"
>> depends on AC97_BUS
>> - depends on GPIOLIB
>> help
>> This enables support for the Philips UCB1400 core functions.
>> The UCB1400 is an AC97 audio codec.
>
> That dependency was added there later, I got email from Andrew Morton from
> 22.9.2008 23:44 adding that there, go ask him about it. CCed.
The header file exports functions which have gpio in its name. However I
did not find any users in tree.
Andrew, do you remember the reason why GPIOLIB got added as a dependency?
Sebastian
next prev parent reply other threads:[~2009-01-08 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 11:06 [RFC] mfd/ucb1400: don't depend on gpiolib Sebastian Andrzej Siewior
2009-01-08 12:25 ` Marek Vasut
2009-01-08 12:37 ` Sebastian Andrzej Siewior [this message]
2009-01-08 12:39 ` Sebastian Andrzej Siewior
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=4965F37B.6040304@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-input@vger.kernel.org \
--cc=marek.vasut@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).