linux-kernel - Re: [PATCH] jfs: fix indentation on if statement

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: <557098FD.8090208@oracle.com>
Date:	Thu, 04 Jun 2015 13:29:17 -0500
From:	Dave Kleikamp <dave.kleikamp@...cle.com>
To:	Colin King <colin.king@...onical.com>,
	jfs-discussion@...ts.sourceforge.net
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] jfs: fix indentation on if statement

On 06/04/2015 11:57 AM, Colin King wrote:
> From: Colin Ian King <colin.king@...onical.com>
> 
> The if statement and closing brace are indented by 1
> extra space, so remove this extra spacing.  Cosmetic
> change only.

Thanks. Pushed to jfs-next.

> 
> Signed-off-by: Colin Ian King <colin.king@...onical.com>
> ---
>  fs/jfs/inode.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/jfs/inode.c b/fs/jfs/inode.c
> index 070dc4b..28d69fa 100644
> --- a/fs/jfs/inode.c
> +++ b/fs/jfs/inode.c
> @@ -133,11 +133,11 @@ int jfs_write_inode(struct inode *inode, struct writeback_control *wbc)
>  	 * It has been committed since the last change, but was still
>  	 * on the dirty inode list.
>  	 */
> -	 if (!test_cflag(COMMIT_Dirty, inode)) {
> +	if (!test_cflag(COMMIT_Dirty, inode)) {
>  		/* Make sure committed changes hit the disk */
>  		jfs_flush_journal(JFS_SBI(inode->i_sb)->log, wait);
>  		return 0;
> -	 }
> +	}
>  
>  	if (jfs_commit_inode(inode, wait)) {
>  		jfs_err("jfs_write_inode: jfs_commit_inode failed!");
> 
--
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/