linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jimmy Li <coder.liss@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH]staging:iio:ad2s1200 fix missing parenthesis in a for statment.
Date: Sat, 26 Apr 2014 11:04:46 +0100	[thread overview]
Message-ID: <535B84BE.8020005@kernel.org> (raw)
In-Reply-To: <20140425025229.GA12200@gmail.com>

On 25/04/14 03:52, Jimmy Li wrote:
> Signed-off-by: Jimmy Li <coder.liss@gmail.com>

Applied to the fixes-togreg branch of iio.git

Thanks,
> ---
>   drivers/staging/iio/resolver/ad2s1200.c |    3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/resolver/ad2s1200.c b/drivers/staging/iio/resolver/ad2s1200.c
> index e2b4820..017d2f8 100644
> --- a/drivers/staging/iio/resolver/ad2s1200.c
> +++ b/drivers/staging/iio/resolver/ad2s1200.c
> @@ -107,7 +107,7 @@ static int ad2s1200_probe(struct spi_device *spi)
>   	int pn, ret = 0;
>   	unsigned short *pins = spi->dev.platform_data;
>
> -	for (pn = 0; pn < AD2S1200_PN; pn++)
> +	for (pn = 0; pn < AD2S1200_PN; pn++) {
>   		ret = devm_gpio_request_one(&spi->dev, pins[pn], GPIOF_DIR_OUT,
>   					    DRV_NAME);
>   		if (ret) {
> @@ -115,6 +115,7 @@ static int ad2s1200_probe(struct spi_device *spi)
>   							pins[pn]);
>   			return ret;
>   		}
> +	}
>   	indio_dev = devm_iio_device_alloc(&spi->dev, sizeof(*st));
>   	if (!indio_dev)
>   		return -ENOMEM;
>


      reply	other threads:[~2014-04-26 10:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  2:52 [PATCH]staging:iio:ad2s1200 fix missing parenthesis in a for statment Jimmy Li
2014-04-26 10:04 ` 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=535B84BE.8020005@kernel.org \
    --to=jic23@kernel.org \
    --cc=coder.liss@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sachin.kamat@linaro.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).