linux-kernel - [PATCH -mm] gpio: fix x86 build problem: gpio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 31 Dec 2007 11:10:16 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	David Brownell <david-b@...bell.net>, florian@...nwrt.org
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: [PATCH -mm] gpio: fix x86 build problem: gpio_keys

On Mon, 31 Dec 2007 10:40:27 -0800 David Brownell wrote:

> On Monday 31 December 2007, Randy Dunlap wrote:
> >   CC      drivers/input/keyboard/gpio_keys.o
> > In file included from /local/linsrc/linux-2.6.24-rc6-mm1/drivers/input/keyboard/gpio_keys.c:27:
> > include2/asm/gpio.h:4:18: error: gpio.h: No such file or directory
> 
> Find whatever broken patch selected (on x86_64)
> 
>    CONFIG_GENERIC_GPIO=y
> 
> without actually providing that support (by providing <asm/gpio.h> and
> an implementation backing it up).  That's the patch which broke those
> various GPIO-dependant drivers.

OK, thanks for the direction.

---

From: Randy Dunlap <randy.dunlap@...cle.com>

X86_RDC321X is X86_32, so make it depend on X86_32 so that
X86_64 random configs don't try to build RDC and fail.

Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
---
 arch/x86/Kconfig |    1 +
 1 file changed, 1 insertion(+)

--- linux-2.6.24-rc6-mm1.orig/arch/x86/Kconfig
+++ linux-2.6.24-rc6-mm1/arch/x86/Kconfig
@@ -297,6 +297,7 @@ config X86_ES7000
 
 config X86_RDC321X
 	bool "RDC R-321x SoC"
+	depends on X86_32
 	select M486
 	select X86_REBOOTFIXUPS
 	select GENERIC_GPIO
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/