From: Alexandre Courbot <gnurou@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Ralf Baechle <ralf@linux-mips.org>
Cc: uclinux-dist-devel@blackfin.uclinux.org,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
linux-mips@linux-mips.org, gnurou@gmail.com,
Alexandre Courbot <acourbot@nvidia.com>
Subject: [RFC 3/3] blackfin: force use of gpiolib
Date: Sun, 17 Mar 2013 22:42:03 +0900 [thread overview]
Message-ID: <1363527723-32713-4-git-send-email-acourbot@nvidia.com> (raw)
In-Reply-To: <1363527723-32713-1-git-send-email-acourbot@nvidia.com>
Set the GENERIC_GPIO option to false by default and force the use of
gpiolib instead of making it optional, to prepare for the removal of
GENERIC_GPIO.
Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
---
arch/blackfin/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/blackfin/Kconfig b/arch/blackfin/Kconfig
index c3f2e0b..20e203a 100644
--- a/arch/blackfin/Kconfig
+++ b/arch/blackfin/Kconfig
@@ -31,7 +31,7 @@ config BLACKFIN
select HAVE_OPROFILE
select HAVE_PERF_EVENTS
select ARCH_HAVE_CUSTOM_GPIO_H
- select ARCH_WANT_OPTIONAL_GPIOLIB
+ select ARCH_REQUIRE_GPIOLIB
select HAVE_UID16
select VIRT_TO_BUS
select ARCH_WANT_IPC_PARSE_VERSION
@@ -56,7 +56,7 @@ config ZONE_DMA
def_bool y
config GENERIC_GPIO
- def_bool y
+ def_bool n
config FORCE_MAX_ZONEORDER
int
--
1.8.2
prev parent reply other threads:[~2013-03-17 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 13:42 [RFC 0/3] Removal of GENERIC_GPIO from architecture code Alexandre Courbot
2013-03-17 13:42 ` [RFC 1/3] mips: pnx833x: remove requirement for GENERIC_GPIO Alexandre Courbot
2013-03-17 13:42 ` [RFC 2/3] m68k: coldfire: use gpiolib Alexandre Courbot
2013-03-21 5:35 ` Greg Ungerer
2013-03-17 13:42 ` Alexandre Courbot [this message]
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=1363527723-32713-4-git-send-email-acourbot@nvidia.com \
--to=gnurou@gmail.com \
--cc=acourbot@nvidia.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®