From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, calestyo@scientia.net, ahferroin7@gmail.com,
1i5t5.duncan@cox.net
Subject: [PATCH 0/7] Let user specify the kernel version for features
Date: Wed, 25 Nov 2015 20:08:13 +0800 [thread overview]
Message-ID: <1448453300-8449-1-git-send-email-anand.jain@oracle.com> (raw)
Sometimes users may want to have a btrfs to be supported on multiple
kernel version. A simple example, USB drive can be used with multiple
system running different kernel versions. Or in a data center a SAN
LUN could be mounted on any system with different kernel version.
Thanks for providing comments and feedback.
Further to it, here below is a set of patch which will introduce, to
specify a kernel version so that default features can be set based on
what features were supported at that kernel version.
First of all to let user know what features was supported at what kernel
version. Patch 1/7 updates -O list-all which will list the feature with
version.
As we didn't maintain the sysfs and progs feature names consistent, so
to avoid confusion Patch 2/7 displays sysfs feature name as well again
in the list-all output.
Next, Patch 3,4,5/7 are helper functions.
Patch 6,7/7 provides the -O comp=<version> for mkfs.btrfs and
btrfs-convert respectively
Thanks, Anand
Anand Jain (7):
btrfs-progs: show the version for -O list-all
btrfs-progs: add kernel alias for each of the features in the list
btrfs-progs: make is_numerical non static
btrfs-progs: check for numerical in version_to_code()
btrfs-progs: introduce framework version to features
btrfs-progs: add -O comp= option for mkfs.btrfs
btrfs-progs: add -O comp= option for btrfs-convert
btrfs-convert.c | 21 +++++++++++++++++++++
cmds-replace.c | 11 -----------
mkfs.c | 24 ++++++++++++++++++++++--
utils.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++++-----
utils.h | 2 ++
5 files changed, 98 insertions(+), 18 deletions(-)
--
2.6.2
next reply other threads:[~2015-11-25 12:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 12:08 Anand Jain [this message]
2015-11-25 12:08 ` [PATCH 1/7] btrfs-progs: show the version for -O list-all Anand Jain
2015-11-25 12:08 ` [PATCH 2/7] btrfs-progs: add kernel alias for each of the features in the list Anand Jain
2015-11-25 13:36 ` [PATCH V1.1 " Anand Jain
2015-11-25 18:11 ` [PATCH " Liu Bo
2015-11-25 22:52 ` Anand Jain
2015-11-25 12:08 ` [PATCH 3/7] btrfs-progs: make is_numerical non static Anand Jain
2015-11-25 12:08 ` [PATCH 4/7] btrfs-progs: check for numerical in version_to_code() Anand Jain
2015-11-25 12:08 ` [PATCH 5/7] btrfs-progs: introduce framework version to features Anand Jain
2015-11-25 12:08 ` [PATCH 6/7] btrfs-progs: add -O comp= option for mkfs.btrfs Anand Jain
2015-11-25 12:08 ` [PATCH 7/7] btrfs-progs: add -O comp= option for btrfs-convert Anand Jain
2015-11-26 2:02 ` [PATCH 0/7] Let user specify the kernel version for features Qu Wenruo
2015-11-26 6:07 ` Anand Jain
2015-11-26 6:53 ` Qu Wenruo
2015-11-26 11:18 ` Anand Jain
2015-11-26 12:31 ` Qu Wenruo
2015-11-26 22:17 ` Anand Jain
2015-11-27 0:44 ` Qu Wenruo
2015-11-27 8:41 ` Anand Jain
2015-11-29 1:21 ` Qu Wenruo
2015-11-30 4:54 ` Anand Jain
2015-11-30 5:46 ` Qu Wenruo
2016-02-03 10:50 ` David Sterba
2016-02-04 1:12 ` Qu Wenruo
2016-02-04 1:42 ` Chris Mason
2015-11-30 5:44 ` potential btrfs-progs clean up Anand Jain
2015-11-30 6:12 ` Qu Wenruo
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=1448453300-8449-1-git-send-email-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=1i5t5.duncan@cox.net \
--cc=ahferroin7@gmail.com \
--cc=calestyo@scientia.net \
--cc=dsterba@suse.cz \
--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).