From: Nikolay Borisov <nborisov@suse.com>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>, linux-btrfs@vger.kernel.org
Cc: Dave Sterba <DSterba@suse.com>
Subject: Re: [PATCH] btrfs: Derive compression type from extent map during reads
Date: Wed, 27 Apr 2022 12:06:37 +0300 [thread overview]
Message-ID: <7deead89-3be0-2ac2-cbb2-05171911cbe4@suse.com> (raw)
In-Reply-To: <20220426134734.dxxdrf2hutbmimtc@fiona>
On 26.04.22 г. 16:47 ч., Goldwyn Rodrigues wrote:
> Derive the compression type from extent map as opposed to the bio flags
> passed. This makes it more precise and not reliant on function
> parameters.
>
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
This patch also makes extent_compress_type unused so it can be removed.
Also extent_set_compress_type also becomes redundant and can be removed.
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
<snip>
next prev parent reply other threads:[~2022-04-27 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 13:47 [PATCH] btrfs: Derive compression type from extent map during reads Goldwyn Rodrigues
2022-04-27 9:06 ` Nikolay Borisov [this message]
2022-04-27 20:24 ` David Sterba
2022-04-28 16:42 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2022-04-26 13:46 Goldwyn Rodrigues
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=7deead89-3be0-2ac2-cbb2-05171911cbe4@suse.com \
--to=nborisov@suse.com \
--cc=DSterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rgoldwyn@suse.de \
/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