public inbox for cgroups@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] nfs: include xattr.h from fs/nfs/nfs3proc.c
@ 2014-02-03 19:31 Tejun Heo
       [not found] ` <20140203193107.GH30250-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
  0 siblings, 1 reply; 4+ messages in thread
From: Tejun Heo @ 2014-02-03 19:31 UTC (permalink / raw)
  To: J. Bruce Fields, linux-nfs-u79uwXL29TY76Z2rM5mHXA
  Cc: Li Zefan, containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA,
	cgroups-u79uwXL29TY76Z2rM5mHXA

fs/nfs/nfs3proc.c is making use of xattr but was getting linux/xattr.h
indirectly through linux/cgroup.h, which will soon drop the inclusion
of xattr.h.  Explicitly include linux/xattr.h from nfs3proc.c so that
compilation doesn't fail when linux/cgroup.h drops linux/xattr.h.

As the following cgroup changes will depend on these changes, it
probably would be easier to route this through cgroup branch.  Would
that be okay?

Signed-off-by: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "J. Bruce Fields" <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
Cc: linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
---
 fs/nfs/nfs3proc.c |    1 +
 1 file changed, 1 insertion(+)

--- a/fs/nfs/nfs3proc.c
+++ b/fs/nfs/nfs3proc.c
@@ -18,6 +18,7 @@
 #include <linux/lockd/bind.h>
 #include <linux/nfs_mount.h>
 #include <linux/freezer.h>
+#include <linux/xattr.h>
 
 #include "iostat.h"
 #include "internal.h"

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-02-03 20:45 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-03 19:31 [PATCH] nfs: include xattr.h from fs/nfs/nfs3proc.c Tejun Heo
     [not found] ` <20140203193107.GH30250-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2014-02-03 19:48   ` Trond Myklebust
     [not found]     ` <F2DD11A7-8D32-4E1E-BB4D-7384F0932B2D-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-02-03 20:43       ` Tejun Heo
2014-02-03 20:45   ` Tejun Heo

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox