Re: [RFC][PATCH] trimming includes from linux/security.h

[Tetsuo Handa]

Al Viro wrote:
> 	linux/security.h pulls a lot of garbage; most of it can be avoided
> by several more struct ....; added in there,

Does it make sense to create a header file that contains only "struct ....;"
lines? A lot of "struct ....;" lines are used for avoiding compiler warning.
This results in LXR (linux cross reference) showing like

Defined as a struct type in:

    * security/selinux/include/avc.h, line 35
    * fs/udf/udfdecl.h, line 78
    * fs/isofs/isofs.h, line 108
    * fs/gfs2/bmap.h, line 15
    * fs/gfs2/dir.h, line 16
    * fs/xfs/xfs_acl.h, line 21
    * fs/xfs/xfs_vnodeops.h, line 7
    * fs/freevxfs/vxfs_extern.h, line 44
    * include/linux/net.h, line 67
    * include/linux/exportfs.h, line 7
    * include/linux/seq_file.h, line 13
    * include/linux/mm.h, line 245
    * include/linux/syscalls.h, line 16
    * include/linux/reiserfs_xattr.h, line 32
    * include/linux/xattr.h, line 64
    * include/linux/cgroup.h, line 24
    * include/linux/fs.h, line 749
    * include/linux/audit.h, line 375
    * include/linux/cdev.h, line 9
    * include/linux/cred.h, line 23
    * include/linux/mtd/blktrans.h, line 31
    * include/linux/generic_acl.h, line 6
    * include/linux/futex.h, line 127 

and makes it difficult to find the location of actual definition.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/