The patch titled
gpio: fix build on CONFIG_GPIO_SYSFS=n
has been added to the -mm tree. Its filename is
gpio-fix-build-on-config_gpio_sysfs=n.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: gpio: fix build on CONFIG_GPIO_SYSFS=n
From: Atsushi Nemoto <anemo@xxxxxxxxxxxxx>
If CONFIG_GENERIC_GPIO=y && CONFIG_GPIO_SYSFS=n, gpio_export() in
asm-generic/gpio.h refers -ENOSYS and causes build error.
Signed-off-by: Atsushi Nemoto <anemo@xxxxxxxxxxxxx>
Acked-by: David Brownell <dbrownell@xxxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/asm-generic/gpio.h | 1 +
1 file changed, 1 insertion(+)
diff -puN include/asm-generic/gpio.h~gpio-fix-build-on-config_gpio_sysfs=n include/asm-generic/gpio.h
--- a/include/asm-generic/gpio.h~gpio-fix-build-on-config_gpio_sysfs=n
+++ a/include/asm-generic/gpio.h
@@ -2,6 +2,7 @@
#define _ASM_GENERIC_GPIO_H
#include <linux/types.h>
+#include <linux/errno.h>
#ifdef CONFIG_GPIOLIB
_
Patches currently in -mm which might be from anemo@xxxxxxxxxxxxx are
origin.patch
gpio-fix-build-on-config_gpio_sysfs=n.patch
mtd-jedec_probe-fix-sst-16-bit-chip-detection.patch
mtdpart-separate-main-loop-from-per-partition-code-in-add_mtd_partition.patch
mtdpart-handle-most-checkpatch-findings.patch
mtdpart-cleanup-and-document-the-erase-region-handling.patch
mtdpart-fix-a-division-by-zero-bug.patch
mtdpart-handle-remaining-checkpatch-findings.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
