From: Christoph Hellwig <hch@infradead.org>
To: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
Cc: djwong@kernel.org, hch@infradead.org, cem@kernel.org,
linux-xfs@vger.kernel.org, ritesh.list@gmail.com,
ojaswin@linux.ibm.com
Subject: Re: [PATCH v1 3/4] xfs: Update lazy counters in xfs_growfs_rt_bmblock()
Date: Tue, 17 Feb 2026 21:55:23 -0800 [thread overview]
Message-ID: <aZVUS2ed5FF6H65H@infradead.org> (raw)
In-Reply-To: <edd86fb5739483fb016fbde304d72bb7325782a0.1770904484.git.nirjhar.roy.lists@gmail.com>
On Thu, Feb 12, 2026 at 07:31:46PM +0530, Nirjhar Roy (IBM) wrote:
> Update lazy counters in xfs_growfs_rt_bmblock() similar to the way it
> is done xfs_growfs_data_private().
Please explain why you're doing this. I think it would also be helpful
to bring over a comment similar to the one in xfs_growfs_data_private.
next prev parent reply other threads:[~2026-02-18 5:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 14:01 [PATCH v1 0/4] xfs: Misc changes to XFS realtime Nirjhar Roy (IBM)
2026-02-12 14:01 ` [PATCH v1 1/4] xfs: Fix xfs_last_rt_bmblock() Nirjhar Roy (IBM)
2026-02-18 5:53 ` Christoph Hellwig
2026-02-18 7:47 ` Nirjhar Roy (IBM)
2026-02-12 14:01 ` [PATCH v1 2/4] xfs: Update sb_frextents when lazy count is set Nirjhar Roy (IBM)
2026-02-18 5:54 ` Christoph Hellwig
2026-02-18 8:49 ` Nirjhar Roy (IBM)
2026-02-19 6:38 ` Christoph Hellwig
2026-02-19 6:46 ` Nirjhar Roy (IBM)
2026-02-19 6:51 ` Christoph Hellwig
2026-02-19 7:05 ` Nirjhar Roy (IBM)
2026-02-19 7:07 ` Christoph Hellwig
2026-02-19 7:09 ` Nirjhar Roy (IBM)
2026-02-12 14:01 ` [PATCH v1 3/4] xfs: Update lazy counters in xfs_growfs_rt_bmblock() Nirjhar Roy (IBM)
2026-02-18 5:55 ` Christoph Hellwig [this message]
2026-02-18 7:48 ` Nirjhar Roy (IBM)
2026-02-12 14:01 ` [PATCH v1 4/4] xfs: Add some comments in some macros Nirjhar Roy (IBM)
2026-02-18 5:56 ` Christoph Hellwig
2026-02-18 7:50 ` Nirjhar Roy (IBM)
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=aZVUS2ed5FF6H65H@infradead.org \
--to=hch@infradead.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nirjhar.roy.lists@gmail.com \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.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