what constitutes an "unused" include/linux header file?

[Robert P. J. Day]

  one of my cleanup scripts tries to specifically identify header
files under include/linux that appear to be entirely unused (that is,
un-included) from anywhere else in the source tree, but one of those
files it claims is unused is if_wanpipe.h, which has the following
properties:

$ grep -r "if_wanpipe.h" *
Documentation/networking/wan-router.txt:        if_wanpipe.h    WANPIPE Socket definitions
include/linux/Kbuild:unifdef-y += if_wanpipe.h
include/linux/if_wanpipe.h:* if_wanpipe.h       Header file for the Sangoma AF_WANPIPE Socket
$

  in short, while it exists, it isn't "include"d by anyone, but it's
still passed to userspace.  what's the protocol for having header
files in the kernel source tree that aren't actually used in any way
by the kernel, but are simply handed off to userspace?  certainly, it
might be handy to have some of these headers, but is it really the
responsibility of the kernel to be a helpful storage centre to make
userspace programming easier?  just curious.  (that's not the only
header file like that.)

rday
--


========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

Home page:                                         http://crashcourse.ca
Fedora Cookbook:    http://crashcourse.ca/wiki/index.php/Fedora_Cookbook
========================================================================
--
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/