[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56B06252.5080504@oracle.com>
Date: Tue, 02 Feb 2016 16:01:22 +0800
From: Ryan Ding <ryan.ding@...cle.com>
To: Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Mark Fasheh <mfasheh@...e.com>,
Joel Becker <jlbec@...lplan.org>
CC: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
ocfs2-devel@....oracle.com
Subject: Re: [PATCH] ocfs2: fix build warning
On 02/02/2016 02:46 PM, Sudip Mukherjee wrote:
> We were getting build warning about:
> /fs/ocfs2/file.c: In function ‘ocfs2_file_write_iter’:
> fs/ocfs2/file.c:2198:1: warning: label ‘relock’ defined but not used
>
> The previous commit has cleaned up the code for direct io and removed
> the jump instruction to relock, but missed removing the label which is
> unused now.
>
> Fixes: 1a46f12e5071 ("ocfs2: code clean up for direct io")
> Cc: Ryan Ding <ryan.ding@...cle.com>
> Signed-off-by: Sudip Mukherjee <sudip@...torindia.org>
Reviewed-by: Ryan Ding<ryan.ding@...cle.com>
> ---
> fs/ocfs2/file.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c
> index 41c506e..c18ab45 100644
> --- a/fs/ocfs2/file.c
> +++ b/fs/ocfs2/file.c
> @@ -2195,7 +2195,6 @@ static ssize_t ocfs2_file_write_iter(struct kiocb *iocb,
>
> inode_lock(inode);
>
> -relock:
> /*
> * Concurrent O_DIRECT writes are allowed with
> * mount_option "coherency=buffered".
Powered by blists - more mailing lists