[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190624145341.GG5387@magnolia>
Date: Mon, 24 Jun 2019 07:53:41 -0700
From: "Darrick J. Wong" <darrick.wong@...cle.com>
To: Christoph Hellwig <hch@....de>
Cc: Damien Le Moal <Damien.LeMoal@....com>,
Andreas Gruenbacher <agruenba@...hat.com>,
linux-xfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 03/12] xfs: fix a comment typo in xfs_submit_ioend
On Mon, Jun 24, 2019 at 07:52:44AM +0200, Christoph Hellwig wrote:
> The fail argument is long gone, update the comment.
>
> Signed-off-by: Christoph Hellwig <hch@....de>
Looks ok,
Reviewed-by: Darrick J. Wong <darrick.wong@...cle.com>
--D
> ---
> fs/xfs/xfs_aops.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
> index 9cceb90e77c5..dc60aec0c5a7 100644
> --- a/fs/xfs/xfs_aops.c
> +++ b/fs/xfs/xfs_aops.c
> @@ -626,7 +626,7 @@ xfs_map_blocks(
> * reference to the ioend to ensure that the ioend completion is only done once
> * all bios have been submitted and the ioend is really done.
> *
> - * If @fail is non-zero, it means that we have a situation where some part of
> + * If @status is non-zero, it means that we have a situation where some part of
> * the submission process has failed after we have marked paged for writeback
> * and unlocked them. In this situation, we need to fail the bio and ioend
> * rather than submit it to IO. This typically only happens on a filesystem
> --
> 2.20.1
>
Powered by blists - more mailing lists