public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Fabian Frederick <fabf@skynet.be>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] isofs: remove unused functions
Date: Fri, 31 Oct 2014 15:40:45 +0100	[thread overview]
Message-ID: <20141031144045.GA10437@quack.suse.cz> (raw)
In-Reply-To: <1414757628-16326-1-git-send-email-sudipm.mukherjee@gmail.com>

On Fri 31-10-14 17:43:48, Sudip Mukherjee wrote:
> commit "5b71ecfa78271d5c576f17156ed8a53981c1ecbb" removed the use
> two functions isofs_hash() and isofs_dentry_cmp() , but their
> definition was not removed.
> So, as these functions are not used anywhere so it is safe to
> remove them. It has been build tested after removing.
  Thanks for the patch. One note though - after your patch
isofs_hash_common() is called from a single place so there's no point to
have that function. You can just inline it in isofs_hash_ms(). Please do
that when we are messing with the code.

								Honza
> 
> Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> ---
>  fs/isofs/inode.c | 17 -----------------
>  1 file changed, 17 deletions(-)
> 
> diff --git a/fs/isofs/inode.c b/fs/isofs/inode.c
> index 859a309..fe839b9 100644
> --- a/fs/isofs/inode.c
> +++ b/fs/isofs/inode.c
> @@ -29,13 +29,9 @@
>  #define BEQUIET
>  
>  static int isofs_hashi(const struct dentry *parent, struct qstr *qstr);
> -static int isofs_hash(const struct dentry *parent, struct qstr *qstr);
>  static int isofs_dentry_cmpi(const struct dentry *parent,
>  		const struct dentry *dentry,
>  		unsigned int len, const char *str, const struct qstr *name);
> -static int isofs_dentry_cmp(const struct dentry *parent,
> -		const struct dentry *dentry,
> -		unsigned int len, const char *str, const struct qstr *name);
>  
>  #ifdef CONFIG_JOLIET
>  static int isofs_hashi_ms(const struct dentry *parent, struct qstr *qstr);
> @@ -254,25 +250,12 @@ static int isofs_dentry_cmp_common(
>  }
>  
>  static int
> -isofs_hash(const struct dentry *dentry, struct qstr *qstr)
> -{
> -	return isofs_hash_common(qstr, 0);
> -}
> -
> -static int
>  isofs_hashi(const struct dentry *dentry, struct qstr *qstr)
>  {
>  	return isofs_hashi_common(qstr, 0);
>  }
>  
>  static int
> -isofs_dentry_cmp(const struct dentry *parent, const struct dentry *dentry,
> -		unsigned int len, const char *str, const struct qstr *name)
> -{
> -	return isofs_dentry_cmp_common(len, str, name, 0, 0);
> -}
> -
> -static int
>  isofs_dentry_cmpi(const struct dentry *parent, const struct dentry *dentry,
>  		unsigned int len, const char *str, const struct qstr *name)
>  {
> -- 
> 1.8.1.2
> 
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2014-10-31 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 12:13 [PATCH] isofs: remove unused functions Sudip Mukherjee
2014-10-31 14:40 ` Jan Kara [this message]
2014-10-31 17:01 ` Al Viro
2014-10-31 17:08   ` Sudip Mukherjee

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=20141031144045.GA10437@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=fabf@skynet.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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