mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Gaosheng Cui <cuigaosheng1@huawei.com>, shaggy@kernel.org
Cc: jfs-discussion@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jfs: remove unused declarations for jfs
Date: Mon, 17 Oct 2022 16:08:18 -0500	[thread overview]
Message-ID: <700ae03f-12d2-8c01-2e20-8db797b4d5ef@oracle.com> (raw)
In-Reply-To: <20220909065055.1154080-1-cuigaosheng1@huawei.com>

Applied.

Thanks,
Shaggy

On 9/9/22 1:50AM, Gaosheng Cui wrote:
> extRealloc(), xtRelocate(), xtDelete() and extFill() have been
> removed since commit e471e5942c00 ("fs/jfs: Remove dead code"),
> so remove them.
> 
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
> ---
>   fs/jfs/jfs_extent.h | 2 --
>   fs/jfs/jfs_xtree.h  | 4 ----
>   2 files changed, 6 deletions(-)
> 
> diff --git a/fs/jfs/jfs_extent.h b/fs/jfs/jfs_extent.h
> index 1c984214e95e..a0ee4ccea66e 100644
> --- a/fs/jfs/jfs_extent.h
> +++ b/fs/jfs/jfs_extent.h
> @@ -10,9 +10,7 @@
>   	(addressPXD(&(JFS_IP(ip)->ixpxd)) + lengthPXD(&(JFS_IP(ip)->ixpxd)) - 1)
>   
>   extern int	extAlloc(struct inode *, s64, s64, xad_t *, bool);
> -extern int	extFill(struct inode *, xad_t *);
>   extern int	extHint(struct inode *, s64, xad_t *);
> -extern int	extRealloc(struct inode *, s64, xad_t *, bool);
>   extern int	extRecord(struct inode *, xad_t *);
>   
>   #endif	/* _H_JFS_EXTENT */
> diff --git a/fs/jfs/jfs_xtree.h b/fs/jfs/jfs_xtree.h
> index 142caafc73b1..ad7592191d76 100644
> --- a/fs/jfs/jfs_xtree.h
> +++ b/fs/jfs/jfs_xtree.h
> @@ -96,12 +96,8 @@ extern int xtInsert(tid_t tid, struct inode *ip,
>   extern int xtExtend(tid_t tid, struct inode *ip, s64 xoff, int xlen,
>   		    int flag);
>   extern int xtUpdate(tid_t tid, struct inode *ip, struct xad *nxad);
> -extern int xtDelete(tid_t tid, struct inode *ip, s64 xoff, int xlen,
> -		    int flag);
>   extern s64 xtTruncate(tid_t tid, struct inode *ip, s64 newsize, int type);
>   extern s64 xtTruncate_pmap(tid_t tid, struct inode *ip, s64 committed_size);
> -extern int xtRelocate(tid_t tid, struct inode *ip,
> -		      xad_t * oxad, s64 nxaddr, int xtype);
>   extern int xtAppend(tid_t tid,
>   		    struct inode *ip, int xflag, s64 xoff, int maxblocks,
>   		    int *xlenp, s64 * xaddrp, int flag);

      reply	other threads:[~2022-10-17 21:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  6:50 Gaosheng Cui
2022-10-17 21:08 ` Dave Kleikamp [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=700ae03f-12d2-8c01-2e20-8db797b4d5ef@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=cuigaosheng1@huawei.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@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®