mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Harkes <jaharkes@cs.cmu.edu>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/coda: remove useless varible 'err'
Date: Mon, 9 Nov 2020 09:41:41 -0500	[thread overview]
Message-ID: <20201109144141.63uvxmjs2sokrqt2@cs.cmu.edu> (raw)
In-Reply-To: <1604674628-52464-1-git-send-email-alex.shi@linux.alibaba.com>

On Fri, Nov 06, 2020 at 10:57:08PM +0800, Alex Shi wrote:
> The variable is unused and cause gcc warning:
> fs/coda/file.c:241:6: warning: variable ‘err’ set but not used
> [-Wunused-but-set-variable]
> So let's remove it.
> Signed-off-by: Alex Shi <alex.shi@linux.alibaba.com>
> Cc: Jan Harkes <jaharkes@cs.cmu.edu> 
> Cc: coda@cs.cmu.edu 
> Cc: codalist@coda.cs.cmu.edu 
> Cc: linux-kernel@vger.kernel.org 

Looks good to me.

Acked-by: Jan Harkes <jaharkes@cs.cmu.edu>

> ---
>  fs/coda/file.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/fs/coda/file.c b/fs/coda/file.c
> index 128d63df5bfb..31a7ba383cb2 100644
> --- a/fs/coda/file.c
> +++ b/fs/coda/file.c
> @@ -238,11 +238,10 @@ int coda_release(struct inode *coda_inode, struct file *coda_file)
>  	struct coda_file_info *cfi;
>  	struct coda_inode_info *cii;
>  	struct inode *host_inode;
> -	int err;
>  
>  	cfi = coda_ftoc(coda_file);
>  
> -	err = venus_close(coda_inode->i_sb, coda_i2f(coda_inode),
> +	venus_close(coda_inode->i_sb, coda_i2f(coda_inode),
>  			  coda_flags, coda_file->f_cred->fsuid);
>  
>  	host_inode = file_inode(cfi->cfi_container);
> -- 
> 1.8.3.1
> 
> 

      reply	other threads:[~2020-11-09 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 14:57 Alex Shi
2020-11-09 14:41 ` Jan Harkes [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=20201109144141.63uvxmjs2sokrqt2@cs.cmu.edu \
    --to=jaharkes@cs.cmu.edu \
    --cc=alex.shi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®