From: "jonathan.cameron@gmail.com" <jic23@cam.ac.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Jeff Mahoney <jeffm@suse.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging/iio: Make IIO depend on GENERIC_HARDIRQS
Date: Tue, 31 May 2011 12:01:06 +0100 [thread overview]
Message-ID: <8eace637-27d2-41c5-bcbd-0087d6c75a75@email.android.com> (raw)
In-Reply-To: <1306834660-15374-1-git-send-email-geert@linux-m68k.org>
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>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.
Dratt We talked about this and thought S390 was the only non generic hard irq left. Should have played safe sorry!
>Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Jonathan Cameron <jic23@cam.ac.uk>
>---
> drivers/staging/iio/Kconfig | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
>diff --git a/drivers/staging/iio/Kconfig b/drivers/staging/iio/Kconfig
>index f96d5b5..d329635 100644
>--- a/drivers/staging/iio/Kconfig
>+++ b/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
>--
>1.7.0.4
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2011-05-31 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 9:37 Geert Uytterhoeven
2011-05-31 11:01 ` jonathan.cameron@gmail.com [this message]
2011-05-31 19:34 ` Geert Uytterhoeven
2011-06-26 8:10 ` Geert Uytterhoeven
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=8eace637-27d2-41c5-bcbd-0087d6c75a75@email.android.com \
--to=jic23@cam.ac.uk \
--cc=devel@driverdev.osuosl.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@suse.de \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®