linux-kernel - Re: [PATCH] staging: iio: adc: ad7192: fix space before , coding style issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 26 Dec 2014 10:42:27 +0000
From:	Jonathan Cameron <jic23@...nel.org>
To:	Mohammad Jamal <md.jamalmohiuddin@...il.com>, lars@...afoo.de
CC:	Michael.Hennerich@...log.com, knaack.h@....de, pmeerw@...erw.net,
	gregkh@...uxfoundation.org, linux-iio@...r.kernel.org,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: iio: adc: ad7192: fix space before , coding
 style issue

On 21/12/14 12:35, Mohammad Jamal wrote:
> This patch solves the space before , error of the checkpatch.pl
> 
> Signed-off-by: Mohammad Jamal <md.jamalmohiuddin@...il.com>
Also fixed in that earlier patch from Zachery.
> ---
>  drivers/staging/iio/adc/ad7192.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/iio/adc/ad7192.c b/drivers/staging/iio/adc/ad7192.c
> index f6526aa..6f8ce6c 100644
> --- a/drivers/staging/iio/adc/ad7192.c
> +++ b/drivers/staging/iio/adc/ad7192.c
> @@ -612,7 +612,7 @@ static int ad7192_probe(struct spi_device *spi)
>  	const struct ad7192_platform_data *pdata = spi->dev.platform_data;
>  	struct ad7192_state *st;
>  	struct iio_dev *indio_dev;
> -	int ret , voltage_uv = 0;
> +	int ret, voltage_uv = 0;
>  
>  	if (!pdata) {
>  		dev_err(&spi->dev, "no platform data?\n");
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/