From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] fixup: Btrfs: change wait_dev_flush() return type to bool v2
Date: Tue, 28 Mar 2023 20:28:55 +0200 [thread overview]
Message-ID: <20230328182855.GO10580@twin.jikos.cz> (raw)
In-Reply-To: <be5e43a3f8333200a69ba85e9c62eb943871c811.1679980900.git.anand.jain@oracle.com>
On Tue, Mar 28, 2023 at 01:31:27PM +0800, Anand Jain wrote:
> A fixup for the patch:
> Btrfs: change wait_dev_flush() return type to bool v2
>
> In v2:
> Fixes:
> Update write_dev_flush() to return false upon success and true upon errors.
> Remove the local variable ret in barrier_all_devices().
> Correct the bug where errors_wait was incremented upon success.
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> Dave,
>
> I am sending this patch as a fix-up while I am still waiting to hear
> whether patch 4/4 will be dropped. If you would prefer to have this
> series sent as v2 with patch 4/4 removed, I can do that.
Ok let's do test_and_clear(), I'll fold the fixup and add the series to
misc-next. Thanks.
next prev parent reply other threads:[~2023-03-28 18:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 9:53 [PATCH 0/4] btrfs: optimize disks flush code Anand Jain
2023-03-27 9:53 ` [PATCH 1/4] btrfs: move last_flush_error to write_dev_flush and wait_dev_flush Anand Jain
2023-03-27 9:53 ` [PATCH 2/4] btrfs: opencode check_barrier_error() Anand Jain
2023-03-27 9:53 ` [PATCH 3/4] Btrfs: change wait_dev_flush() return type to bool Anand Jain
2023-03-27 17:11 ` David Sterba
2023-03-28 2:58 ` Anand Jain
2023-03-27 23:52 ` kernel test robot
2023-03-28 5:31 ` [PATCH] fixup: Btrfs: change wait_dev_flush() return type to bool v2 Anand Jain
2023-03-28 18:28 ` David Sterba [this message]
2023-03-27 9:53 ` [PATCH 4/4] btrfs: use test_and_clear_bit() in wait_dev_flush() Anand Jain
2023-03-27 17:14 ` David Sterba
2023-03-28 5:05 ` Anand Jain
2023-03-28 18:33 ` 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=20230328182855.GO10580@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.