linux-kernel - Re: [PATCH] staging: lustre: Fix spacing error in libcfs

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]

Message-ID: <20150118000001.GA10033@kroah.com>
Date:	Sat, 17 Jan 2015 16:00:01 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Nickolaus Woodruff <nickolauswoodruff@...il.com>
Cc:	andreas.dilger@...el.com, oleg.drokin@...el.com,
	HPDD-discuss@...ts.01.org, linux-kernel@...r.kernel.org,
	devel@...verdev.osuosl.org
Subject: Re: [PATCH] staging: lustre: Fix spacing error in libcfs_string.c

On Sun, Jan 11, 2015 at 01:44:03PM -0500, Nickolaus Woodruff wrote:
> This patch fixes the following checkpatch.pl error in libcfs_string.c:
> 
> ERROR: spaces required around that '='
> 
> Signed-off-by: Nickolaus Woodruff <nickolauswoodruff@...il.com>
> ---
>  drivers/staging/lustre/lustre/libcfs/libcfs_string.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/lustre/lustre/libcfs/libcfs_string.c b/drivers/staging/lustre/lustre/libcfs/libcfs_string.c
> index fb88733..e67a18d 100644
> --- a/drivers/staging/lustre/lustre/libcfs/libcfs_string.c
> +++ b/drivers/staging/lustre/lustre/libcfs/libcfs_string.c
> @@ -132,7 +132,7 @@ char *cfs_firststr(char *str, size_t size)
>  		++end;
>  	}
>  
> -	*end= '\0';
> +	*end = '\0';
>  out:
>  	return str;
>  }
> -- 
> 1.9.1

Someone already sent this patch before you did, sorry.

greg k-h
--
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/