All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Lauss <manuel.lauss@googlemail.com>
To: Ralf Baechle <ralf@linux-mips.org>,
	Florian Fainelli <florian@openwrt.org>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: MTX build failure
Date: Fri, 28 Aug 2009 10:53:34 +0200	[thread overview]
Message-ID: <4A979B0E.106@gmail.com> (raw)
In-Reply-To: <20090828074709.GA11637@linux-mips.org>

Ralf Baechle wrote:
>   CC      drivers/input/keyboard/gpio_keys.o
> /home/ralf/src/linux/linux-mips/drivers/input/keyboard/gpio_keys.c: In function ‘gpio_keys_probe’:
> /home/ralf/src/linux/linux-mips/drivers/input/keyboard/gpio_keys.c:123: error: implicit declaration of function ‘gpio_request’
> /home/ralf/src/linux/linux-mips/drivers/input/keyboard/gpio_keys.c:135: error: implicit declaration of function ‘gpio_free’
> make[5]: *** [drivers/input/keyboard/gpio_keys.o] Error 1
> make[4]: *** [drivers/input/keyboard] Error 2
> make[3]: *** [drivers/input] Error 2
> make[2]: *** [drivers] Error 2
> make[1]: *** [sub-make] Error 2

Either something like the patch below, or adding stubs for
gpio_request/gpio_free to asm/mach-au1x00/gpio-au1000.h in the
CONFIG_GPIOLIB=n case should fix it.

diff --git a/arch/mips/alchemy/Kconfig b/arch/mips/alchemy/Kconfig
index 1e0a6df..f0c930a 100644
--- a/arch/mips/alchemy/Kconfig
+++ b/arch/mips/alchemy/Kconfig
@@ -20,6 +20,7 @@ config MIPS_MTX1
 	select HW_HAS_PCI
 	select SOC_AU1500
 	select SYS_SUPPORTS_LITTLE_ENDIAN
+	select GPIOLIB

 config MIPS_BOSPORUS
 	bool "Alchemy Bosporus board"


	Manuel Lauss

  parent reply	other threads:[~2009-08-28  8:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28  7:47 MTX build failure Ralf Baechle
2009-08-28  8:26 ` Florian Fainelli
2009-08-28  8:53 ` Manuel Lauss [this message]
2009-08-28  9:07   ` Florian Fainelli
2009-08-28  9:26   ` Manuel Lauss
2009-08-28  9:57     ` Florian Fainelli
2009-08-28 10:10       ` Manuel Lauss
2009-08-28 13:14     ` Ralf Baechle

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=4A979B0E.106@gmail.com \
    --to=manuel.lauss@googlemail.com \
    --cc=florian@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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 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.