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
| ||
|
Date: Fri, 23 Jan 2015 11:21:41 +0100 From: Paul Bolle <pebolle@...cali.nl> To: Jassi Brar <jaswinder.singh@...aro.org> Cc: Valentin Rothberg <valentinrothberg@...il.com>, Andy Green <andy.green@...aro.org>, Vincent Yang <Vincent.Yang@...fujitsu.com>, Tetsuya Nuriya <nuriya.tetsuya@...fujitsu.com>, Linus Walleij <linus.walleij@...aro.org>, Alexandre Courbot <gnurou@...il.com>, linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org Subject: gpio: ARCH_MB86S7X? Jassi, Your commit 0da094d82c27 ("gpio: Add Fujitsu MB86S7x GPIO driver") is included in today's linux-next (ie, next-20150123). I noticed because a script I use to check linux-next spotted a problem in it. That commit added the Kconfig symbol GPIO_MB86S7X and made it depend on ARCH_MB86S7X. But there's no Kconfig symbol ARCH_MB86S7X in linux-next. I assume a patch to add that symbol is queued somewhere. Is that correct? Please note that I actually managed to cross-compile drivers/gpio/gpio-mb86s7x.c with this command: make ARCH=arm CROSS_COMPILE=arm-linux-gnu- EXTRA_CFLAGS="-DCONFIG_GPIOLIB=y" drivers/gpio/gpio-mb86s7x.o So, for what it's worth, that dependency appears to be not needed to build this driver. Thanks, Paul Bolle -- 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/
Powered by blists - more mailing lists