From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@kernel.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
David Sterba <dsterba@suse.com>
Subject: Re: [PATCH] Btrfs: prevent send failures and crashes due to concurrent relocation
Date: Mon, 13 May 2019 17:45:34 +0200 [thread overview]
Message-ID: <20190513154534.GC3138@twin.jikos.cz> (raw)
In-Reply-To: <CAL3q7H4nrAJSwXoX9c5LX2oFb-CFdHQ-enMON3ZqgNWoRqP33g@mail.gmail.com>
On Mon, May 13, 2019 at 03:04:13PM +0100, Filipe Manana wrote:
> David, are you picking this for this merge window or have any other plans?
Post-merge window, with the other fixes.
next prev parent reply other threads:[~2019-05-13 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 15:44 [PATCH] Btrfs: prevent send failures and crashes due to concurrent relocation fdmanana
2019-04-24 8:56 ` Nikolay Borisov
2019-04-24 9:13 ` Filipe Manana
2019-05-13 14:04 ` Filipe Manana
2019-05-13 15:45 ` David Sterba [this message]
2019-05-13 16:32 ` David Sterba
2019-05-13 16:43 ` Filipe Manana
2019-05-13 18:00 ` David Sterba
2019-06-06 13:24 ` Filipe Manana
2019-06-13 9:24 ` Filipe Manana
2019-06-13 17:14 ` David Sterba
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=20190513154534.GC3138@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@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