From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: [PATCH] xfs: remove unused FI_ flags
Date: Fri, 15 Nov 2013 09:38:48 -0800 [thread overview]
Message-ID: <20131115173848.GA24872@infradead.org> (raw)
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
fs/xfs/xfs_vnode.h | 9 ---------
1 file changed, 9 deletions(-)
Index: xfs/fs/xfs/xfs_vnode.h
===================================================================
--- xfs.orig/fs/xfs/xfs_vnode.h 2013-10-11 17:03:21.244338013 +0100
+++ xfs/fs/xfs/xfs_vnode.h 2013-10-22 07:21:09.236045186 +0100
@@ -35,15 +35,6 @@ struct attrlist_cursor_kern;
{ IO_INVIS, "INVIS"}
/*
- * Flush/Invalidate options for vop_toss/flush/flushinval_pages.
- */
-#define FI_NONE 0 /* none */
-#define FI_REMAPF 1 /* Do a remapf prior to the operation */
-#define FI_REMAPF_LOCKED 2 /* Do a remapf prior to the operation.
- Prevent VM access to the pages until
- the operation completes. */
-
-/*
* Some useful predicates.
*/
#define VN_MAPPED(vp) mapping_mapped(vp->i_mapping)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-11-15 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 17:38 Christoph Hellwig [this message]
2013-11-15 17:47 ` [PATCH] xfs: remove unused FI_ flags Eric Sandeen
2013-12-04 21:53 ` Ben Myers
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=20131115173848.GA24872@infradead.org \
--to=hch@infradead.org \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox