From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 1/2] btrfs: define compression levels statically
Date: Wed, 21 Aug 2019 18:55:30 +0800 [thread overview]
Message-ID: <08f16559-a8f9-f147-2919-2f0ceb8f317e@oracle.com> (raw)
In-Reply-To: <d4972ff57eb3ef57c616f5f7545f92d0cab7e12e.1566313756.git.dsterba@suse.com>
On 21/8/19 12:17 AM, David Sterba wrote:
> The maximum and default levels do not change and can be defined
> directly. The set_level callback was a temporary solution and will be
> removed.
>
> Signed-off-by: David Sterba <dsterba@suse.com>
Reviewed-by: Anand Jain <anand.jain@oracle.com>
next prev parent reply other threads:[~2019-08-21 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 16:17 [PATCH v2 0/2] Compression level API cleanups David Sterba
2019-08-20 16:17 ` [PATCH v2 1/2] btrfs: define compression levels statically David Sterba
2019-08-21 10:55 ` Anand Jain [this message]
2019-08-20 16:17 ` [PATCH v2 2/2] btrfs: compression: replace set_level callbacks by a common helper David Sterba
2019-08-21 10:16 ` Anand Jain
2019-08-21 10:53 ` David Sterba
2019-08-21 6:52 ` [PATCH v2 0/2] Compression level API cleanups Nikolay Borisov
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=08f16559-a8f9-f147-2919-2f0ceb8f317e@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.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).