From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@kernel.org>
Cc: dsterba@suse.cz, linux-btrfs <linux-btrfs@vger.kernel.org>,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH v3 0/4] Btrfs: make ranged fsyncs always respect the given range
Date: Fri, 13 Mar 2020 14:17:17 +0100 [thread overview]
Message-ID: <20200313131717.GL12659@twin.jikos.cz> (raw)
In-Reply-To: <CAL3q7H42gkjx83Eqd1sfvtqOcj0k4BjLLr-k-C=mA2COcw1dEA@mail.gmail.com>
On Fri, Mar 13, 2020 at 11:01:35AM +0000, Filipe Manana wrote:
> > > Filipe Manana (4):
> > > Btrfs: fix missing file extent item for hole after ranged fsync
> > > Btrfs: add helper to get the end offset of a file extent item
> > > Btrfs: factor out inode items copy loop from btrfs_log_inode()
> > > Btrfs: make ranged full fsyncs more efficient
> >
> > Moved from for-next to misc-next, thanks.
>
> Btw, Josef's reviewed-by tag is missing in the changelog of patch 4
> (however there's an unusual reviewed-by tag from you).
I meant to put my rev-by to the cleanup patches, for the 4th patch I'll
update it.
prev parent reply other threads:[~2020-03-13 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 12:41 [PATCH v3 0/4] Btrfs: make ranged fsyncs always respect the given range fdmanana
2020-03-09 12:41 ` [PATCH v3 1/4] Btrfs: fix missing file extent item for hole after ranged fsync fdmanana
2020-03-09 12:41 ` [PATCH v3 2/4] Btrfs: add helper to get the end offset of a file extent item fdmanana
2020-03-09 12:41 ` [PATCH v3 3/4] Btrfs: factor out inode items copy loop from btrfs_log_inode() fdmanana
2020-03-09 12:41 ` [PATCH v3 4/4] Btrfs: make ranged full fsyncs more efficient fdmanana
2020-03-11 17:44 ` [PATCH v3 0/4] Btrfs: make ranged fsyncs always respect the given range Josef Bacik
2020-03-12 20:33 ` David Sterba
2020-03-13 11:01 ` Filipe Manana
2020-03-13 13:17 ` 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=20200313131717.GL12659@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--cc=josef@toxicpanda.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).