From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com,
David Sterba <dsterba@suse.cz>
Subject: Re: [PATCH 0/3][v2] clean up how we mark block groups read only
Date: Wed, 29 Jan 2020 14:45:21 +0100 [thread overview]
Message-ID: <20200129134520.GD3929@twin.jikos.cz> (raw)
In-Reply-To: <cda6acc2-b91e-c6f6-757e-92b5628cec29@gmx.com>
On Wed, Jan 29, 2020 at 02:05:33PM +0800, Qu Wenruo wrote:
> Hi David,
>
> This is also an important patchset, mostly to solve the false ENOSPC
> from btrfs_inc_block_group_ro() calls.
> One obvious example is btrfs/182 test case.
>
> Would you mind to merge it for misc-next?
No, I don't mind and various other patchsets are next first to be merged
once merge window ends.
prev parent reply other threads:[~2020-01-29 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 14:07 [PATCH 0/3][v2] clean up how we mark block groups read only Josef Bacik
2020-01-17 14:07 ` [PATCH 1/3] btrfs: check rw_devices, not num_devices for restriping Josef Bacik
2020-01-17 14:07 ` [PATCH 2/3] btrfs: fix force usage in inc_block_group_ro Josef Bacik
2020-01-17 14:07 ` [PATCH 3/3] btrfs: use btrfs_can_overcommit " Josef Bacik
2020-01-29 6:05 ` [PATCH 0/3][v2] clean up how we mark block groups read only Qu Wenruo
2020-01-29 13:45 ` 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=20200129134520.GD3929@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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