public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: cem@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: fix an overly long line in xfs_rtgroup_calc_geometry
Date: Fri, 9 Jan 2026 08:20:59 -0800	[thread overview]
Message-ID: <20260109162059.GQ15551@frogsfrogsfrogs> (raw)
In-Reply-To: <20260109151901.2376971-2-hch@lst.de>

On Fri, Jan 09, 2026 at 04:18:54PM +0100, Christoph Hellwig wrote:
> Signed-off-by: Christoph Hellwig <hch@lst.de>

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

--D

> ---
>  fs/xfs/libxfs/xfs_rtgroup.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_rtgroup.c b/fs/xfs/libxfs/xfs_rtgroup.c
> index 5a3d0dc6ae1b..be16efaa6925 100644
> --- a/fs/xfs/libxfs/xfs_rtgroup.c
> +++ b/fs/xfs/libxfs/xfs_rtgroup.c
> @@ -83,7 +83,8 @@ xfs_rtgroup_calc_geometry(
>  	xfs_rtbxlen_t		rextents)
>  {
>  	rtg->rtg_extents = __xfs_rtgroup_extents(mp, rgno, rgcount, rextents);
> -	rtg_group(rtg)->xg_block_count = rtg->rtg_extents * mp->m_sb.sb_rextsize;
> +	rtg_group(rtg)->xg_block_count =
> +		rtg->rtg_extents * mp->m_sb.sb_rextsize;
>  	rtg_group(rtg)->xg_min_gbno = xfs_rtgroup_min_block(mp, rgno);
>  }
>  
> -- 
> 2.47.3
> 
> 

  reply	other threads:[~2026-01-09 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 15:18 [PATCH 1/2] xfs: mark __xfs_rtgroup_extents static Christoph Hellwig
2026-01-09 15:18 ` [PATCH 2/2] xfs: fix an overly long line in xfs_rtgroup_calc_geometry Christoph Hellwig
2026-01-09 16:20   ` Darrick J. Wong [this message]
2026-01-09 16:20 ` [PATCH 1/2] xfs: mark __xfs_rtgroup_extents static Darrick J. Wong
2026-01-13 13:10 ` 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=20260109162059.GQ15551@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@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