From: Andreas Philipp <philipp.andreas@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Andreas Philipp <philipp.andreas@gmail.com>, lizf@cn.fujitsu.com
Subject: [PATCH 4/5] Test the additional ioctl.
Date: Wed, 13 Apr 2011 11:12:13 +0200 [thread overview]
Message-ID: <1302685934-15737-5-git-send-email-philipp.andreas@gmail.com> (raw)
In-Reply-To: <1302685934-15737-1-git-send-email-philipp.andreas@gmail.com>
Signed-off-by: Andreas Philipp <philipp.andreas@gmail.com>
---
ioctl-test.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/ioctl-test.c b/ioctl-test.c
index 7cf3bc2..1c27d61 100644
--- a/ioctl-test.c
+++ b/ioctl-test.c
@@ -22,6 +22,7 @@ unsigned long ioctls[] = {
BTRFS_IOC_INO_LOOKUP,
BTRFS_IOC_DEFAULT_SUBVOL,
BTRFS_IOC_SPACE_INFO,
+ BTRFS_IOC_SNAP_CREATE_V2,
0 };
int main(int ac, char **av)
--
1.7.4.1
next prev parent reply other threads:[~2011-04-13 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 9:12 [PATCH 0/5] Add user-space support for read-only snapshot creation Andreas Philipp
2011-04-13 9:12 ` [PATCH 1/5] Add support for read-only subvolumes Andreas Philipp
2011-04-13 9:12 ` [PATCH 2/5] Support the new parameters in do_clone(int argc, char** argv) Andreas Philipp
2011-04-13 9:12 ` [PATCH 3/5] Added support for an additional ioctl Andreas Philipp
2011-04-13 9:12 ` Andreas Philipp [this message]
2011-04-13 9:12 ` [PATCH 5/5] Updated documentation for btrfs subvolume snapshot Andreas Philipp
2011-04-25 12:16 Read Only snapshots Chris Mason
2011-04-25 13:47 ` [PATCH 0/5] Add user-space support for read-only snapshot creation Andreas Philipp
2011-04-25 13:48 ` [PATCH 4/5] Test the additional ioctl Andreas Philipp
[not found] <There is kernel side support for the creation of read-only snapshots>
2011-04-26 8:02 ` [PATCH v2 0/5] Add user-space support for read-only snapshot creation Andreas Philipp
2011-04-26 8:02 ` [PATCH 4/5] Test the additional ioctl Andreas Philipp
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=1302685934-15737-5-git-send-email-philipp.andreas@gmail.com \
--to=philipp.andreas@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.