From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com, wqu@suse.com
Subject: Re: [PATCH 0/4][v2] clean up how we mark block groups read only
Date: Fri, 10 Jan 2020 12:35:09 +0800 [thread overview]
Message-ID: <d4838402-3acd-1fea-6d61-7ff806629e1a@gmx.com> (raw)
In-Reply-To: <20191203195139.GC2734@twin.jikos.cz>
[-- Attachment #1.1: Type: text/plain, Size: 666 bytes --]
On 2019/12/4 上午3:51, David Sterba wrote:
> On Tue, Nov 26, 2019 at 11:25:52AM -0500, Josef Bacik wrote:
>> v1->v2:
>> - Fixed the typo where I wasn't checking against total_bytes.
>> - Added the force check to the read only list addition check at the top.
>> - Fixed the comment stating that sinfo_used + num_bytes should be <=
>> total_bytes, that's not the case at all.
>> - Added the various reviewed-by's.
>
> I'm applying 1 and 2 to misc-next, 3 and 4 once the comments are
> addressed.
>
Hi Josef,
Would you mind to update the patchset?
If you're busy I could keep your author and do the misc work of patch 3/4.
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-10 4:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 16:25 [PATCH 0/4][v2] clean up how we mark block groups read only Josef Bacik
2019-11-26 16:25 ` [PATCH 1/4] btrfs: don't pass system_chunk into can_overcommit Josef Bacik
2019-11-26 16:25 ` [PATCH 2/4] btrfs: kill min_allocable_bytes in inc_block_group_ro Josef Bacik
2019-11-27 10:45 ` Qu Wenruo
2019-11-26 16:25 ` [PATCH 3/4] btrfs: fix force usage " Josef Bacik
2019-11-27 10:45 ` Qu Wenruo
2019-12-03 19:50 ` David Sterba
2019-11-26 16:25 ` [PATCH 4/4] btrfs: use btrfs_can_overcommit " Josef Bacik
2019-11-27 10:48 ` Qu Wenruo
2019-12-03 19:51 ` [PATCH 0/4][v2] clean up how we mark block groups read only David Sterba
2020-01-10 4:35 ` Qu Wenruo [this message]
2020-01-10 16:05 ` Josef Bacik
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=d4838402-3acd-1fea-6d61-7ff806629e1a@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@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