linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Mohammad Jamal <md.jamalmohiuddin@gmail.com>, lars@metafoo.de
Cc: Michael.Hennerich@analog.com, knaack.h@gmx.de, pmeerw@pmeerw.net,
	gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging : iio: meter: ade7759: fix space before , coding style issue
Date: Fri, 26 Dec 2014 10:39:42 +0000	[thread overview]
Message-ID: <549D3AEE.5020400@kernel.org> (raw)
In-Reply-To: <1419165769-29782-1-git-send-email-md.jamalmohiuddin@gmail.com>

On 21/12/14 12:42, Mohammad Jamal wrote:
> This patch solves the space before , coding style issue found by
> checkpatch in ade7759.c
> 
> Signed-off-by: Mohammad Jamal <md.jamalmohiuddin@gmail.com>
Fixed by Zachery Warren back in November.  I'm a bit behind with
sending stuff upstream so won't have hit anything other than the
togreg branch of iio.git just yet.

Patch was:

[PATCH] drivers:staging:iio: fix checkpatch complaint about space before comma
Thanks,

Jonathan
> ---
>  drivers/staging/iio/meter/ade7759.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/iio/meter/ade7759.c b/drivers/staging/iio/meter/ade7759.c
> index 7d21743..b0c7dbc 100644
> --- a/drivers/staging/iio/meter/ade7759.c
> +++ b/drivers/staging/iio/meter/ade7759.c
> @@ -116,7 +116,7 @@ static int ade7759_spi_read_reg_40(struct device *dev,
>  
>  	mutex_lock(&st->buf_lock);
>  	st->tx[0] = ADE7759_READ_REG(reg_address);
> -	memset(&st->tx[1], 0 , 5);
> +	memset(&st->tx[1], 0, 5);
>  
>  	ret = spi_sync_transfer(st->us, xfers, ARRAY_SIZE(xfers));
>  	if (ret) {
> 


      reply	other threads:[~2014-12-26 10:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21 12:42 [PATCH] staging : iio: meter: ade7759: fix space before , coding style issue Mohammad Jamal
2014-12-26 10:39 ` 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=549D3AEE.5020400@kernel.org \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=md.jamalmohiuddin@gmail.com \
    --cc=pmeerw@pmeerw.net \
    /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).