public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Yang Xu <xuyang2018.jy@fujitsu.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: Fix comments mentioning xfs_ialloc
Date: Fri, 17 Dec 2021 08:54:43 -0800	[thread overview]
Message-ID: <20211217165443.GF27664@magnolia> (raw)
In-Reply-To: <1639706519-2239-1-git-send-email-xuyang2018.jy@fujitsu.com>

On Fri, Dec 17, 2021 at 10:01:59AM +0800, Yang Xu wrote:
> Since kernel commit 1abcf261016e ("xfs: move on-disk inode allocation out of xfs_ialloc()"),
> xfs_ialloc has been renamed to xfs_init_new_inode. So update this in comments.
> 
> Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>

Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

> ---
>  fs/xfs/xfs_icache.c | 3 ++-
>  fs/xfs/xfs_iops.c   | 6 +++---
>  2 files changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/xfs/xfs_icache.c b/fs/xfs/xfs_icache.c
> index e1472004170e..39758015f302 100644
> --- a/fs/xfs/xfs_icache.c
> +++ b/fs/xfs/xfs_icache.c
> @@ -770,7 +770,8 @@ xfs_iget(
>  
>  	/*
>  	 * If we have a real type for an on-disk inode, we can setup the inode
> -	 * now.	 If it's a new inode being created, xfs_ialloc will handle it.
> +	 * now.	 If it's a new inode being created, xfs_init_new_inode will
> +	 * handle it.
>  	 */
>  	if (xfs_iflags_test(ip, XFS_INEW) && VFS_I(ip)->i_mode != 0)
>  		xfs_setup_existing_inode(ip);
> diff --git a/fs/xfs/xfs_iops.c b/fs/xfs/xfs_iops.c
> index a607d6aca5c4..f2ceb6c3fc50 100644
> --- a/fs/xfs/xfs_iops.c
> +++ b/fs/xfs/xfs_iops.c
> @@ -1332,9 +1332,9 @@ xfs_diflags_to_iflags(
>   * Initialize the Linux inode.
>   *
>   * When reading existing inodes from disk this is called directly from xfs_iget,
> - * when creating a new inode it is called from xfs_ialloc after setting up the
> - * inode. These callers have different criteria for clearing XFS_INEW, so leave
> - * it up to the caller to deal with unlocking the inode appropriately.
> + * when creating a new inode it is called from xfs_init_new_inode after setting
> + * up the inode. These callers have different criteria for clearing XFS_INEW, so
> + * leave it up to the caller to deal with unlocking the inode appropriately.
>   */
>  void
>  xfs_setup_inode(
> -- 
> 2.23.0
> 

      reply	other threads:[~2021-12-17 16:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17  2:01 [PATCH] xfs: Fix comments mentioning xfs_ialloc Yang Xu
2021-12-17 16:54 ` Darrick J. Wong [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=20211217165443.GF27664@magnolia \
    --to=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=xuyang2018.jy@fujitsu.com \
    /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