From: "Darrick J. Wong" <djwong@kernel.org>
To: Yan Zhen <yanzhen@vivo.com>
Cc: chandan.babu@oracle.com, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org, opensource.kernel@vivo.com
Subject: Re: [PATCH v1] xfs: scrub: convert comma to semicolon
Date: Mon, 16 Sep 2024 10:00:01 -0700 [thread overview]
Message-ID: <20240916170001.GC182194@frogsfrogsfrogs> (raw)
In-Reply-To: <20240910122842.3269966-1-yanzhen@vivo.com>
On Tue, Sep 10, 2024 at 08:28:42PM +0800, Yan Zhen wrote:
> Replace a comma between expression statements by a semicolon.
>
> Signed-off-by: Yan Zhen <yanzhen@vivo.com>
Looks good,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/xfs/scrub/ialloc_repair.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/scrub/ialloc_repair.c b/fs/xfs/scrub/ialloc_repair.c
> index a00ec7ae1..c8d2196a0 100644
> --- a/fs/xfs/scrub/ialloc_repair.c
> +++ b/fs/xfs/scrub/ialloc_repair.c
> @@ -657,7 +657,7 @@ xrep_ibt_build_new_trees(
> * Start by setting up the inobt staging cursor.
> */
> fsbno = XFS_AGB_TO_FSB(sc->mp, sc->sa.pag->pag_agno,
> - XFS_IBT_BLOCK(sc->mp)),
> + XFS_IBT_BLOCK(sc->mp));
> xrep_newbt_init_ag(&ri->new_inobt, sc, &XFS_RMAP_OINFO_INOBT, fsbno,
> XFS_AG_RESV_NONE);
> ri->new_inobt.bload.claim_block = xrep_ibt_claim_block;
> @@ -678,7 +678,7 @@ xrep_ibt_build_new_trees(
> resv = XFS_AG_RESV_NONE;
>
> fsbno = XFS_AGB_TO_FSB(sc->mp, sc->sa.pag->pag_agno,
> - XFS_FIBT_BLOCK(sc->mp)),
> + XFS_FIBT_BLOCK(sc->mp));
> xrep_newbt_init_ag(&ri->new_finobt, sc, &XFS_RMAP_OINFO_INOBT,
> fsbno, resv);
> ri->new_finobt.bload.claim_block = xrep_fibt_claim_block;
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2024-09-16 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 12:28 [PATCH v1] xfs: scrub: convert comma to semicolon Yan Zhen
2024-09-16 17:00 ` Darrick J. Wong [this message]
2024-09-27 18:45 ` Carlos Maiolino
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=20240916170001.GC182194@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=yanzhen@vivo.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