Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Gabriel Niebler <gniebler@suse.com>
Cc: Nikolay Borisov <nborisov@suse.com>,
	linux-btrfs@vger.kernel.org, dsterba@suse.com
Subject: Re: [PATCH v6] btrfs: Turn delayed_nodes_tree into an XArray
Date: Mon, 9 May 2022 21:51:51 +0200	[thread overview]
Message-ID: <20220509195151.GG18596@twin.jikos.cz> (raw)
In-Reply-To: <3de4b25a-9528-a2c5-336e-ac33f1a2692c@suse.com>

On Thu, May 05, 2022 at 09:35:53AM +0200, Gabriel Niebler wrote:
> Should I resend with the small changes outlined below, or will the patch 
> be accepted and the diff folded into it on the maintainer's side?

No need to resend, the fixup has been applied.

      reply	other threads:[~2022-05-09 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  9:43 [PATCH v6] btrfs: Turn delayed_nodes_tree into an XArray Gabriel Niebler
2022-04-26 11:11 ` Nikolay Borisov
2022-04-26 14:31   ` Gabriel Niebler
2022-05-05  7:35     ` Gabriel Niebler
2022-05-09 19:51       ` David Sterba [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=20220509195151.GG18596@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=gniebler@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.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