From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH] staging:iio:iio-trig-bfin-timer: Fix compile error
Date: Sat, 28 Sep 2013 11:46:32 +0100 [thread overview]
Message-ID: <5246B388.2060101@kernel.org> (raw)
In-Reply-To: <1380289838-27029-1-git-send-email-lars@metafoo.de>
On 09/27/13 14:50, Lars-Peter Clausen wrote:
> This patch fixes the following compile errors for the iio-trig-bfin-timer
> driver:
> drivers/staging/iio/trigger/iio-trig-bfin-timer.c: In function ‘iio_bfin_tmr_frequency_store’:
> drivers/staging/iio/trigger/iio-trig-bfin-timer.c:121: error: invalid storage class for function ‘iio_bfin_tmr_frequency_show’
> drivers/staging/iio/trigger/iio-trig-bfin-timer.c:118: warning: ISO C90 forbids mixed declarations and code
> drivers/staging/iio/trigger/iio-trig-bfin-timer.c:135: error: initializer element is not constant
> ...
>
> The issue was introduced in commit e5e26dd5 ("staging: iio: replace
> strict_strto*() with kstrto*()") by leaving an excess opening bracket.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Applied to the togreg branch of iio.git
Thanks,
> ---
> drivers/staging/iio/trigger/iio-trig-bfin-timer.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/trigger/iio-trig-bfin-timer.c b/drivers/staging/iio/trigger/iio-trig-bfin-timer.c
> index ebb189c..26e1ca0 100644
> --- a/drivers/staging/iio/trigger/iio-trig-bfin-timer.c
> +++ b/drivers/staging/iio/trigger/iio-trig-bfin-timer.c
> @@ -91,7 +91,7 @@ static ssize_t iio_bfin_tmr_frequency_store(struct device *dev,
> if (ret)
> return ret;
>
> - if (val > 100000) {
> + if (val > 100000)
> return -EINVAL;
>
> enabled = get_enabled_gptimers() & st->t->bit;
>
prev parent reply other threads:[~2013-09-28 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 13:50 [PATCH] staging:iio:iio-trig-bfin-timer: Fix compile error Lars-Peter Clausen
2013-09-28 10:46 ` Jonathan Cameron [this message]
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=5246B388.2060101@kernel.org \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.