From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH][RFC] Delete export of tty.h to userspace.
Date: Wed, 18 Jul 2007 05:24:28 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707180520040.19434@localhost.localdomain> (raw)
Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>
---
given that the entire contents of include/linux/tty.h is contained
within an "#ifdef __KERNEL__", it seems pointless to export it to
userspace, unless there's some kind of need for that header file to
exist in userspace, even if it's empty.
a quick grep shows that nothing under /usr/include references any
file of the name "tty.h" in any way. thoughts?
diff --git a/include/linux/Kbuild b/include/linux/Kbuild
index 4ff0f57..63de91a 100644
--- a/include/linux/Kbuild
+++ b/include/linux/Kbuild
@@ -328,7 +327,6 @@ unifdef-y += sysctl.h
unifdef-y += tcp.h
unifdef-y += time.h
unifdef-y += timex.h
-unifdef-y += tty.h
unifdef-y += types.h
unifdef-y += udf_fs_i.h
unifdef-y += udp.h
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next reply other threads:[~2007-07-18 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 9:24 Robert P. J. Day [this message]
2007-07-18 20:18 ` Jiri Slaby
2007-07-18 20:33 ` Robert P. J. Day
2007-07-18 22:38 ` Karel Zak
2007-07-19 11:17 ` Robert P. J. Day
2007-07-19 13:57 ` Christoph Hellwig
2007-07-19 15:27 ` Robert P. J. Day
2007-07-19 15:32 ` Jiri Slaby
2007-07-19 16:10 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0707180520040.19434@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®