Linux-XFS Archive mirror
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanbabu@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dave Chinner <david@fromorbit.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: quota radix tree allocations need to be NOFS on insert
Date: Tue, 19 Mar 2024 20:02:59 +0530	[thread overview]
Message-ID: <87ttl2mguf.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <Zfkyk7b_gh7MLwBP@infradead.org>

On Mon, Mar 18, 2024 at 11:37:07 PM -0700, Christoph Hellwig wrote:
> Didn't this just get merged into the for-next tree already?

Yes, This patch was merged into XFS's for-next branch on Monday.

-- 
Chandan

  reply	other threads:[~2024-03-19 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19  0:46 [PATCH] xfs: quota radix tree allocations need to be NOFS on insert Dave Chinner
2024-03-19  6:37 ` Christoph Hellwig
2024-03-19 14:32   ` Chandan Babu R [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-15  1:16 Dave Chinner
2024-03-15  2:28 ` Darrick J. Wong
2024-03-17 21:11 ` 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=87ttl2mguf.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandanbabu@kernel.org \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).