mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: jlbec@evilplan.org, hch@lst.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] configfs: Remove unused configfs_hash_and_remove
Date: Tue, 12 Nov 2024 21:36:45 +0000	[thread overview]
Message-ID: <ZzPKbY3n9gxHebJl@gallifrey> (raw)
In-Reply-To: <20241010205655.278385-1-linux@treblig.org>

* linux@treblig.org (linux@treblig.org) wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
> 
> configfs_hash_and_remove() has been unused since it was added in 2005
> by commit
> 7063fbf22611 ("[PATCH] configfs: User-driven configuration filesystem")
> 
> Remove it.
> 
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>

Ping

Thanks,

Dave

> ---
>  fs/configfs/configfs_internal.h |  2 --
>  fs/configfs/inode.c             | 25 -------------------------
>  2 files changed, 27 deletions(-)
> 
> diff --git a/fs/configfs/configfs_internal.h b/fs/configfs/configfs_internal.h
> index e710a1782382..5c20e83315bc 100644
> --- a/fs/configfs/configfs_internal.h
> +++ b/fs/configfs/configfs_internal.h
> @@ -73,8 +73,6 @@ extern int configfs_make_dirent(struct configfs_dirent *, struct dentry *,
>  				void *, umode_t, int, struct configfs_fragment *);
>  extern int configfs_dirent_is_ready(struct configfs_dirent *);
>  
> -extern void configfs_hash_and_remove(struct dentry * dir, const char * name);
> -
>  extern const unsigned char * configfs_get_name(struct configfs_dirent *sd);
>  extern void configfs_drop_dentry(struct configfs_dirent *sd, struct dentry *parent);
>  extern int configfs_setattr(struct mnt_idmap *idmap,
> diff --git a/fs/configfs/inode.c b/fs/configfs/inode.c
> index dcc22f593e43..1d2e3a5738d1 100644
> --- a/fs/configfs/inode.c
> +++ b/fs/configfs/inode.c
> @@ -216,28 +216,3 @@ void configfs_drop_dentry(struct configfs_dirent * sd, struct dentry * parent)
>  			spin_unlock(&dentry->d_lock);
>  	}
>  }
> -
> -void configfs_hash_and_remove(struct dentry * dir, const char * name)
> -{
> -	struct configfs_dirent * sd;
> -	struct configfs_dirent * parent_sd = dir->d_fsdata;
> -
> -	if (d_really_is_negative(dir))
> -		/* no inode means this hasn't been made visible yet */
> -		return;
> -
> -	inode_lock(d_inode(dir));
> -	list_for_each_entry(sd, &parent_sd->s_children, s_sibling) {
> -		if (!sd->s_element)
> -			continue;
> -		if (!strcmp(configfs_get_name(sd), name)) {
> -			spin_lock(&configfs_dirent_lock);
> -			list_del_init(&sd->s_sibling);
> -			spin_unlock(&configfs_dirent_lock);
> -			configfs_drop_dentry(sd, dir);
> -			configfs_put(sd);
> -			break;
> -		}
> -	}
> -	inode_unlock(d_inode(dir));
> -}
> -- 
> 2.47.0
> 
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2024-11-12 21:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 20:56 linux
2024-11-12 21:36 ` Dr. David Alan Gilbert [this message]
2024-11-14  5:31   ` Christoph Hellwig
2024-11-14 12:17     ` Dr. David Alan Gilbert

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=ZzPKbY3n9gxHebJl@gallifrey \
    --to=linux@treblig.org \
    --cc=hch@lst.de \
    --cc=jlbec@evilplan.org \
    --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®