linux-kernel - header files that are (sort of) referenced

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0703231201530.31459@CPE00045a9c397f-CM001225dbafb6>
Date:	Fri, 23 Mar 2007 12:06:36 -0400 (EDT)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: header files that are (sort of) referenced

  based on that last response, i'm curious about which header files
are technically "unreferenced" in the source tree.

  for example, consider the following two closely-related headers:

  linux/if_wanpipe.h
  linux/if_wanpipe_common.h

that second one is not included by any other file in the tree, so i
would normally call that "unused."  but the first one, while also not
included, *is* exported to userspace.

  i haven't given it much thought but it seems odd to me to include a
header file in the source tree that's technically not *used* by
anything in the source tree, only to export it to userspace.  why not
just keep it in userspace in the first place?

  or is that a silly question?

rday

p.s.  i'm going to assume that if_wanpipe_common.h really *is* useless
and i'll be submitting my final dead header file patch shortly.

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

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/