public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: Carlos Maiolino <cem@kernel.org>,
	"Nirjhar Roy (IBM)" <nirjhar@linux.ibm.com>
Cc: djwong@kernel.org, hch@infradead.org, linux-xfs@vger.kernel.org,
	ritesh.list@gmail.com, ojaswin@linux.ibm.com
Subject: Re: [PATCH v2 0/4] xfs: Misc changes to XFS realtime
Date: Thu, 19 Feb 2026 20:20:21 +0530	[thread overview]
Message-ID: <771efc3b-43bb-4838-9f9b-47341292cf35@gmail.com> (raw)
In-Reply-To: <aZcRxYYpo-DvGxrr@nidhogg.toxiclabs.cc>


On 2/19/26 19:07, Carlos Maiolino wrote:
> On Thu, Feb 19, 2026 at 01:08:48PM +0530, Nirjhar Roy (IBM) wrote:
>> From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
>>
>> This series has a bug fix and adds some missing operations to
>> growfs code in the realtime code. Details are in the commit messages.
>>
>> [v1] -> v2
>> 1. Added RB from Christoph in patch 1 and 4.
>> 2. Updated the commit message in patch 4 ("xfs: Add comments for usages of some macros.")
>> 3. Updated the commit message and added some comments in the code explaining
>>     the change in patch 3("xfs: Update lazy counters in xfs_growfs_rt_bmblock()")
>> 4. Removed patch 2 of [v1] - instead added a comment in xfs_log_sb()
>>     explaining why we are not checking the lazy counter enablement while
>>     updating the free rtextent count (sb_frextents).
>>
>> [v1]- https://lore.kernel.org/all/cover.1770904484.git.nirjhar.roy.lists@gmail.com/
>>
>> Nirjhar Roy (IBM) (4):
>>    xfs: Fix xfs_last_rt_bmblock()
>>    xfs: Add a comment in xfs_log_sb()
>>    xfs: Update lazy counters in xfs_growfs_rt_bmblock()
>>    xfs: Add comments for usages of some macros.
>>
>>   fs/xfs/libxfs/xfs_sb.c |  3 +++
>>   fs/xfs/xfs_linux.h     |  6 ++++++
> Please rebase it on top of current xfs code (preferentially for-next
> branch). xfs_linux.h has been renamed during the merge window.

Okay, done[1]. Thank you for pointing this out.

[1] 
https://lore.kernel.org/all/ed78cfaa48058b00bc93cff93994cfbe0d4ef503.1771512159.git.nirjhar.roy.lists@gmail.com/

--NR

>
> Thanks!
>
>>   fs/xfs/xfs_rtalloc.c   | 39 +++++++++++++++++++++++++++++++++------
>>   3 files changed, 42 insertions(+), 6 deletions(-)
>>
>> -- 
>> 2.43.5
>>
>>
-- 
Nirjhar Roy
Linux Kernel Developer
IBM, Bangalore


      reply	other threads:[~2026-02-19 14:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19  7:38 [PATCH v2 0/4] xfs: Misc changes to XFS realtime Nirjhar Roy (IBM)
2026-02-19  7:38 ` [PATCH v2 1/4] xfs: Fix xfs_last_rt_bmblock() Nirjhar Roy (IBM)
2026-02-19  7:38 ` [PATCH v2 2/4] xfs: Add a comment in xfs_log_sb() Nirjhar Roy (IBM)
2026-02-19  7:44   ` Christoph Hellwig
2026-02-19  7:38 ` [PATCH v2 3/4] xfs: Update lazy counters in xfs_growfs_rt_bmblock() Nirjhar Roy (IBM)
2026-02-19  7:44   ` Christoph Hellwig
2026-02-19  7:38 ` [PATCH v2 4/4] xfs: Add comments for usages of some macros Nirjhar Roy (IBM)
2026-02-19 13:37 ` [PATCH v2 0/4] xfs: Misc changes to XFS realtime Carlos Maiolino
2026-02-19 14:50   ` Nirjhar Roy (IBM) [this message]

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=771efc3b-43bb-4838-9f9b-47341292cf35@gmail.com \
    --to=nirjhar.roy.lists@gmail.com \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nirjhar@linux.ibm.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