The patch titled staging/iio: make IIO depend on GENERIC_HARDIRQS has been removed from the -mm tree. Its filename was staging-iio-make-iio-depend-on-generic_hardirqs.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: staging/iio: make IIO depend on GENERIC_HARDIRQS From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> On m68k (which doesn't support generic hardirqs yet): drivers/staging/iio/industrialio-trigger.c: In function `iio_trigger_poll': drivers/staging/iio/industrialio-trigger.c:180: error: implicit declaration of function `generic_handle_irq' drivers/staging/iio/industrialio-trigger.c: In function `iio_trigger_poll_chained': drivers/staging/iio/industrialio-trigger.c:200: error: implicit declaration of function `handle_nested_irq' drivers/staging/iio/industrialio-trigger.c: In function `iio_trig_release': drivers/staging/iio/industrialio-trigger.c:379: error: implicit declaration of function `irq_modify_status' drivers/staging/iio/industrialio-trigger.c:382: error: implicit declaration of function `irq_set_chip' drivers/staging/iio/industrialio-trigger.c:384: error: implicit declaration of function `irq_set_handler' drivers/staging/iio/industrialio-trigger.c:388: error: implicit declaration of function `irq_free_descs' drivers/staging/iio/industrialio-trigger.c: In function `iio_trig_subirqmask': drivers/staging/iio/industrialio-trigger.c:402: error: implicit declaration of function `irq_data_get_irq_chip' drivers/staging/iio/industrialio-trigger.c:402: warning: initialization makes pointer from integer without a cast drivers/staging/iio/industrialio-trigger.c: In function `iio_trig_subirqunmask': drivers/staging/iio/industrialio-trigger.c:411: warning: initialization makes pointer from integer without a cast drivers/staging/iio/industrialio-trigger.c: In function `iio_allocate_trigger': drivers/staging/iio/industrialio-trigger.c:432: error: implicit declaration of function `irq_alloc_descs' drivers/staging/iio/industrialio-trigger.c:455: error: `handle_simple_irq' undeclared (first use in this function) drivers/staging/iio/industrialio-trigger.c:455: error: (Each undeclared identifier is reported only once drivers/staging/iio/industrialio-trigger.c:455: error: for each function it appears in.) Hence IIO_TRIGGER should depend on GENERIC_HARDIRQS. But as IIO_TRIGGER and IIO_RING_BUFFER form a maze of dependencies and selects, just make the whole IIO subsystem depend on GENERIC_HARDIRQS. This dependency also covers !S390, so that one can be removed again. Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> Cc: Greg Kroah-Hartman <gregkh@xxxxxxx> Cc: Jeff Mahoney <jeffm@xxxxxxxx> Acked-by: Jonathan Cameron <jic23@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/staging/iio/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/staging/iio/Kconfig~staging-iio-make-iio-depend-on-generic_hardirqs drivers/staging/iio/Kconfig --- a/drivers/staging/iio/Kconfig~staging-iio-make-iio-depend-on-generic_hardirqs +++ a/drivers/staging/iio/Kconfig @@ -4,7 +4,7 @@ menuconfig IIO tristate "Industrial I/O support" - depends on !S390 + depends on GENERIC_HARDIRQS help The industrial I/O subsystem provides a unified framework for drivers for many different types of embedded sensors using a _ Patches currently in -mm which might be from geert@xxxxxxxxxxxxxx are mm-nommuc-fix-remap_pfn_range.patch linux-next.patch cris-fix-a-build-error-in-kernel-forkc.patch cris-fix-a-build-error-in-sync_serial_open.patch cris-fix-the-prototype-of-sync_serial_ioctl.patch cris-add-missing-declaration-of-kgdb_init-and-breakpoint.patch fb-fix-potential-deadlock-between-lock_fb_info-and-console_lock.patch m68k-exec-remove-redundant-set_fsuser_ds.patch h8300-m68k-xtensa-__fd_isset-should-return-0-1.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