Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cem@kernel.org>
Cc: "Cc : Hans Holmberg" <hans.holmberg@wdc.com>, linux-xfs@vger.kernel.org
Subject: [PATCH 2/2] xfs: add a comment to describe xfs_gc_bio.victim_rtg
Date: Tue, 28 Jul 2026 10:06:45 +0200	[thread overview]
Message-ID: <20260728080650.1777545-3-hch@lst.de> (raw)
In-Reply-To: <20260728080650.1777545-1-hch@lst.de>

All other fields have comments describing them, add one for this field
as well.

Signed-off-by: Christoph Hellwig <hch@lst.de>
---
 fs/xfs/xfs_zone_gc.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/fs/xfs/xfs_zone_gc.c b/fs/xfs/xfs_zone_gc.c
index e4f70e024632..e2bad83b10f6 100644
--- a/fs/xfs/xfs_zone_gc.c
+++ b/fs/xfs/xfs_zone_gc.c
@@ -103,6 +103,7 @@ struct xfs_gc_bio {
 	/* Open Zone being written to */
 	struct xfs_open_zone		*oz;
 
+	/* Realtime group currently evacuated */
 	struct xfs_rtgroup		*victim_rtg;
 
 	/* Bio used for reads and writes, including the bvec used by it */
-- 
2.53.0


  parent reply	other threads:[~2026-07-28  8:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  8:06 zoned GC fix Christoph Hellwig
2026-07-28  8:06 ` [PATCH 1/2] xfs: add a separate bio_set for spliting GC writes Christoph Hellwig
2026-07-28 15:27   ` Darrick J. Wong
2026-07-29  4:07   ` Damien Le Moal
2026-07-28  8:06 ` Christoph Hellwig [this message]
2026-07-28 15:27   ` [PATCH 2/2] xfs: add a comment to describe xfs_gc_bio.victim_rtg Darrick J. Wong
2026-07-29  4:05   ` Damien Le Moal
  -- strict thread matches above, loose matches on Subject: below --
2026-07-29 13:02 zoned GC fix v2 Christoph Hellwig
2026-07-29 13:02 ` [PATCH 2/2] xfs: add a comment to describe xfs_gc_bio.victim_rtg Christoph Hellwig

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=20260728080650.1777545-3-hch@lst.de \
    --to=hch@lst.de \
    --cc=cem@kernel.org \
    --cc=hans.holmberg@wdc.com \
    --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