Eric Paris 6f3a539e3b fsnotify: use kmem_cache_zalloc to simplify event initialization ... fsnotify event initialization is done entry by entry with almost everything set to either 0 or NULL. Use kmem_cache_zalloc and only initialize things that need non-zero initialization. Also means we don't have to change initialization entries based on the config options. Signed-off-by: Eric Paris <eparis@redhat.com>		2010-07-28 09:58:20 -04:00
..
dnotify	fsnotify: allow addition of duplicate fsnotify marks	2010-07-28 09:58:17 -04:00
inotify	inotify: use container_of instead of casting	2010-07-28 09:58:19 -04:00
fsnotify.c	include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h	2010-03-30 22:02:32 +09:00
fsnotify.h	fsnotify: generic notification queue and waitq	2009-06-11 14:57:53 -04:00
group.c	fsnotify: kzalloc fsnotify groups	2010-07-28 09:58:20 -04:00
inode_mark.c	fsnotify: allow addition of duplicate fsnotify marks	2010-07-28 09:58:17 -04:00
Kconfig	fsnotify: use def_bool in kconfig instead of letting the user choose	2009-07-21 15:26:26 -04:00
Makefile	fsnotify: add marks to inodes so groups can interpret how to handle those inodes	2009-06-11 14:57:53 -04:00
notification.c	fsnotify: use kmem_cache_zalloc to simplify event initialization	2010-07-28 09:58:20 -04:00