aboutsummaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorGravatar Nikolaus Rath <Nikolaus@rath.org>2016-10-17 21:22:47 -0700
committerGravatar Nikolaus Rath <Nikolaus@rath.org>2016-10-20 14:04:37 -0700
commitbcb8568a46a4522d85f9eed626468d98b542e8d8 (patch)
tree23b994c838c878b21edc06e5fa6a325b6fb6ce47 /include
parente869f7cc8ee2b0372da42cf31d08fc21c9f4d862 (diff)
Removed all "Introduced in..." comments
Since FUSE 3 is breaking backwards compatibility, this really does not matter.
Diffstat (limited to 'include')
-rw-r--r--include/fuse.h38
-rw-r--r--include/fuse_common.h15
-rw-r--r--include/fuse_lowlevel.h26
3 files changed, 7 insertions, 72 deletions
diff --git a/include/fuse.h b/include/fuse.h
index 52c915c..52b8698 100644
--- a/include/fuse.h
+++ b/include/fuse.h
@@ -315,8 +315,6 @@ struct fuse_operations {
* directory. Optionally opendir may also return an arbitrary
* filehandle in the fuse_file_info structure, which will be
* passed to readdir, closedir and fsyncdir.
- *
- * Introduced in version 2.3
*/
int (*opendir) (const char *, struct fuse_file_info *);
@@ -334,16 +332,11 @@ struct fuse_operations {
* passes non-zero offset to the filler function. When the buffer
* is full (or an error happens) the filler function will return
* '1'.
- *
- * Introduced in version 2.3
- * The "flags" argument added in version 3.0
*/
int (*readdir) (const char *, void *, fuse_fill_dir_t, off_t,
struct fuse_file_info *, enum fuse_readdir_flags);
/** Release directory
- *
- * Introduced in version 2.3
*/
int (*releasedir) (const char *, struct fuse_file_info *);
@@ -351,8 +344,6 @@ struct fuse_operations {
*
* If the datasync parameter is non-zero, then only the user data
* should be flushed, not the meta data
- *
- * Introduced in version 2.3
*/
int (*fsyncdir) (const char *, int, struct fuse_file_info *);
@@ -362,9 +353,6 @@ struct fuse_operations {
* The return value will passed in the private_data field of
* fuse_context to all file operations and as a parameter to the
* destroy() method.
- *
- * Introduced in version 2.3
- * Changed in version 2.6
*/
void *(*init) (struct fuse_conn_info *conn);
@@ -372,8 +360,6 @@ struct fuse_operations {
* Clean up filesystem
*
* Called on filesystem exit.
- *
- * Introduced in version 2.3
*/
void (*destroy) (void *);
@@ -385,8 +371,6 @@ struct fuse_operations {
* called.
*
* This method is not called under Linux kernel versions 2.4.x
- *
- * Introduced in version 2.5
*/
int (*access) (const char *, int);
@@ -399,8 +383,6 @@ struct fuse_operations {
* If this method is not implemented or under Linux kernel
* versions earlier than 2.6.15, the mknod() and open() methods
* will be called instead.
- *
- * Introduced in version 2.5
*/
int (*create) (const char *, mode_t, struct fuse_file_info *);
@@ -433,8 +415,6 @@ struct fuse_operations {
* Note: if this method is not implemented, the kernel will still
* allow file locking to work locally. Hence it is only
* interesting for network filesystems and similar.
- *
- * Introduced in version 2.6
*/
int (*lock) (const char *, struct fuse_file_info *, int cmd,
struct flock *);
@@ -449,8 +429,6 @@ struct fuse_operations {
* *fi* will be NULL if the file is not currenly opened.
*
* See the utimensat(2) man page for details.
- *
- * Introduced in version 2.6
*/
int (*utimens) (const char *, const struct timespec tv[2],
struct fuse_file_info *fi);
@@ -460,8 +438,6 @@ struct fuse_operations {
*
* Note: This makes sense only for block device backed filesystems
* mounted with the 'blkdev' option
- *
- * Introduced in version 2.6
*/
int (*bmap) (const char *, size_t blocksize, uint64_t *idx);
@@ -477,8 +453,6 @@ struct fuse_operations {
*
* If flags has FUSE_IOCTL_DIR then the fuse_file_info refers to a
* directory file handle.
- *
- * Introduced in version 2.8
*/
int (*ioctl) (const char *, int cmd, void *arg,
struct fuse_file_info *, unsigned int flags, void *data);
@@ -497,8 +471,6 @@ struct fuse_operations {
*
* The callee is responsible for destroying ph with
* fuse_pollhandle_destroy() when no longer in use.
- *
- * Introduced in version 2.8
*/
int (*poll) (const char *, struct fuse_file_info *,
struct fuse_pollhandle *ph, unsigned *reventsp);
@@ -508,8 +480,6 @@ struct fuse_operations {
* Similar to the write() method, but data is supplied in a
* generic buffer. Use fuse_buf_copy() to transfer data to
* the destination.
- *
- * Introduced in version 2.9
*/
int (*write_buf) (const char *, struct fuse_bufvec *buf, off_t off,
struct fuse_file_info *);
@@ -527,8 +497,6 @@ struct fuse_operations {
* location pointed to by bufp. If the buffer contains memory
* regions, they too must be allocated using malloc(). The
* allocated memory will be freed by the caller.
- *
- * Introduced in version 2.9
*/
int (*read_buf) (const char *, struct fuse_bufvec **bufp,
size_t size, off_t off, struct fuse_file_info *);
@@ -549,8 +517,6 @@ struct fuse_operations {
* Note: if this method is not implemented, the kernel will still
* allow file locking to work locally. Hence it is only
* interesting for network filesystems and similar.
- *
- * Introduced in version 2.9
*/
int (*flock) (const char *, struct fuse_file_info *, int op);
@@ -561,8 +527,6 @@ struct fuse_operations {
* file. If this function returns success then any subsequent write
* request to specified range is guaranteed not to fail because of lack
* of space on the file system media.
- *
- * Introduced in version 2.9.1
*/
int (*fallocate) (const char *, int, off_t, off_t,
struct fuse_file_info *);
@@ -589,7 +553,7 @@ struct fuse_context {
/** Private filesystem data */
void *private_data;
- /** Umask of the calling process (introduced in version 2.8) */
+ /** Umask of the calling process */
mode_t umask;
};
diff --git a/include/fuse_common.h b/include/fuse_common.h
index 2a0db73..bdd4a6b 100644
--- a/include/fuse_common.h
+++ b/include/fuse_common.h
@@ -44,27 +44,25 @@ struct fuse_file_info {
writepage */
unsigned int writepage : 1;
- /** Can be filled in by open, to use direct I/O on this file.
- Introduced in version 2.4 */
+ /** Can be filled in by open, to use direct I/O on this file. */
unsigned int direct_io : 1;
/** Can be filled in by open, to indicate, that cached file data
- need not be invalidated. Introduced in version 2.4 */
+ need not be invalidated. */
unsigned int keep_cache : 1;
/** Indicates a flush operation. Set in flush operation, also
maybe set in highlevel lock operation and lowlevel release
- operation. Introduced in version 2.6 */
+ operation. */
unsigned int flush : 1;
/** Can be filled in by open, to indicate that the file is not
- seekable. Introduced in version 2.8 */
+ seekable. */
unsigned int nonseekable : 1;
/* Indicates that flock locks for this file should be
released. If set, lock_owner shall contain a valid value.
- May only be set in ->release(). Introduced in version
- 2.9 */
+ May only be set in ->release(). */
unsigned int flock_release : 1;
/** Padding. Do not use*/
@@ -78,8 +76,7 @@ struct fuse_file_info {
uint64_t lock_owner;
/** Requested poll events. Available in ->poll. Only set on kernels
- which support it. If unsupported, this field is set to zero.
- Introduced in version 3.0 */
+ which support it. If unsupported, this field is set to zero. */
uint32_t poll_events;
};
diff --git a/include/fuse_lowlevel.h b/include/fuse_lowlevel.h
index db15083..8ec95b5 100644
--- a/include/fuse_lowlevel.h
+++ b/include/fuse_lowlevel.h
@@ -766,8 +766,6 @@ struct fuse_lowlevel_ops {
*
* This method is not called under Linux kernel versions 2.4.x
*
- * Introduced in version 2.5
- *
* Valid replies:
* fuse_reply_err
*
@@ -798,8 +796,6 @@ struct fuse_lowlevel_ops {
* versions earlier than 2.6.15, the mknod() and open() methods
* will be called instead.
*
- * Introduced in version 2.5
- *
* Valid replies:
* fuse_reply_create
* fuse_reply_err
@@ -816,8 +812,6 @@ struct fuse_lowlevel_ops {
/**
* Test for a POSIX file lock
*
- * Introduced in version 2.6
- *
* Valid replies:
* fuse_reply_lock
* fuse_reply_err
@@ -843,8 +837,6 @@ struct fuse_lowlevel_ops {
* will still allow file locking to work locally. Hence these are
* only interesting for network filesystems and similar.
*
- * Introduced in version 2.6
- *
* Valid replies:
* fuse_reply_err
*
@@ -864,8 +856,6 @@ struct fuse_lowlevel_ops {
* Note: This makes sense only for block device backed filesystems
* mounted with the 'blkdev' option
*
- * Introduced in version 2.6
- *
* Valid replies:
* fuse_reply_bmap
* fuse_reply_err
@@ -887,8 +877,6 @@ struct fuse_lowlevel_ops {
* restricted ioctls, kernel prepares in/out data area
* according to the information encoded in cmd.
*
- * Introduced in version 2.8
- *
* Valid replies:
* fuse_reply_ioctl_retry
* fuse_reply_ioctl
@@ -912,8 +900,6 @@ struct fuse_lowlevel_ops {
/**
* Poll for IO readiness
*
- * Introduced in version 2.8
- *
* Note: If ph is non-NULL, the client should notify
* when IO readiness events occur by calling
* fuse_lowelevel_notify_poll() with the specified ph.
@@ -952,8 +938,6 @@ struct fuse_lowlevel_ops {
* bufv->off is correctly updated (reflecting the number of
* bytes read from bufv->buf[0]).
*
- * Introduced in version 2.9
- *
* Valid replies:
* fuse_reply_write
* fuse_reply_err
@@ -971,8 +955,6 @@ struct fuse_lowlevel_ops {
/**
* Callback function for the retrieve request
*
- * Introduced in version 2.9
- *
* Valid replies:
* fuse_reply_none
*
@@ -991,8 +973,6 @@ struct fuse_lowlevel_ops {
* See description of the forget function for more
* information.
*
- * Introduced in version 2.9
- *
* Valid replies:
* fuse_reply_none
*
@@ -1008,8 +988,6 @@ struct fuse_lowlevel_ops {
* will still allow file locking to work locally. Hence these are
* only interesting for network filesystems and similar.
*
- * Introduced in version 2.9
- *
* Valid replies:
* fuse_reply_err
*
@@ -1026,8 +1004,6 @@ struct fuse_lowlevel_ops {
* subsequent writes to the specified range shall not fail due to the lack
* of free space on the file system storage media.
*
- * Introduced in version 2.9
- *
* Valid replies:
* fuse_reply_err
*
@@ -1055,8 +1031,6 @@ struct fuse_lowlevel_ops {
* the lookup count of every entry returned by readdirplus(), except "."
* and "..", is incremented by one.
*
- * Introduced in version 3.0
- *
* Valid replies:
* fuse_reply_buf
* fuse_reply_data