From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 3/4] staging:iio:triggers:interrupt trigger - one per platform device.
Date: Sun, 12 May 2013 18:37:31 +0200 [thread overview]
Message-ID: <518FC54B.3090009@metafoo.de> (raw)
In-Reply-To: <1367860863-6863-4-git-send-email-jic23@kernel.org>
[...]
>
> @@ -39,57 +36,48 @@ static const struct iio_trigger_ops iio_interrupt_trigger_ops = {
> static int iio_interrupt_trigger_probe(struct platform_device *pdev)
> {
> struct iio_interrupt_trigger_info *trig_info;
> - struct iio_trigger *trig, *trig2;
> + struct iio_trigger *trig;
> unsigned long irqflags;
> struct resource *irq_res;
> int irq, ret = 0, irq_res_cnt = 0;
> [...]
> + irq_res = platform_get_resource(pdev, IORESOURCE_IRQ, irq_res_cnt);
irq_res_cnt is always zero.
> [...]
next prev parent reply other threads:[~2013-05-12 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 17:20 [RFC PATCH 0/4] iio: Rework the generic trigger-gpio trigger and move out of staging Jonathan Cameron
2013-05-06 17:21 ` [PATCH 1/4] staging:iio:trigger:gpio bug in release of gpio in error path Jonathan Cameron
2013-05-06 17:21 ` [PATCH 2/4] staging:iio:triggers: rename iio-trig-gpio to iio-trig-interrupt Jonathan Cameron
2013-05-06 17:21 ` [PATCH 3/4] staging:iio:triggers:interrupt trigger - one per platform device Jonathan Cameron
2013-05-12 16:37 ` Lars-Peter Clausen [this message]
2013-05-12 18:48 ` Jonathan Cameron
2013-05-06 17:21 ` [PATCH 4/4] iio:triggers:interrupt trigger - move out of staging Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2013-06-02 19:00 [PATCH 0/4 V2] iio: Rework the generic trigger-gpio trigger and " Jonathan Cameron
2013-06-02 19:00 ` [PATCH 3/4] staging:iio:triggers:interrupt trigger - one per platform device Jonathan Cameron
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=518FC54B.3090009@metafoo.de \
--to=lars@metafoo.de \
--cc=jic23@kernel.org \
--cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).