From: David Sterba <dsterba@suse.cz>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs: some refactor and cleanup for NOCOW write paths
Date: Thu, 31 Mar 2022 20:14:47 +0200 [thread overview]
Message-ID: <20220331181447.GG15609@twin.jikos.cz> (raw)
In-Reply-To: <cover.1648650280.git.fdmanana@suse.com>
On Wed, Mar 30, 2022 at 03:31:05PM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> This refactors some duplicated NOCOW checks into a single helper function,
> plus it removes some no longer needed logic. This came out some in progress
> work on the NOCOW paths, but has it's fairly indepedent of that work, it
> is being sent out in a separate patchset.
>
> Filipe Manana (2):
> btrfs: move common NOCOW checks against a file extent into a helper
> btrfs: do not test for free space inode during NOCOW check against
> file extent
Added to misc-next, thanks.
prev parent reply other threads:[~2022-03-31 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 14:31 [PATCH 0/2] btrfs: some refactor and cleanup for NOCOW write paths fdmanana
2022-03-30 14:31 ` [PATCH 1/2] btrfs: move common NOCOW checks against a file extent into a helper fdmanana
2022-03-30 14:31 ` [PATCH 2/2] btrfs: do not test for free space inode during NOCOW check against file extent fdmanana
2022-03-31 18:14 ` 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=20220331181447.GG15609@twin.jikos.cz \
--to=dsterba@suse.cz \
--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