From: Karel Zak <kzak@redhat.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH][RFC] Delete export of tty.h to userspace.
Date: Thu, 19 Jul 2007 00:38:20 +0200 [thread overview]
Message-ID: <20070718223820.GF3181@petra.dvoda.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0707181631340.14452@localhost.localdomain>
On Wed, Jul 18, 2007 at 04:33:12PM -0400, Robert P. J. Day wrote:
> On Wed, 18 Jul 2007, Jiri Slaby wrote:
>
> > Robert P. J. Day napsal(a):
> > > 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?
> >
> > If we decide to remove the file, I would rather go through
> > deprecation of the file with filing an entry in
> > feature-remove-schedule. There still seems to be some users of the
> > file.
>
> i'm curious -- how did you determine that?
$ grep "tty.h" util-linux/sys-utils/cytune.c
#include <linux/tty.h>
... I'll fix it in util-linux-ng.
Karel
--
Karel Zak <kzak@redhat.com>
next prev parent reply other threads:[~2007-07-18 22:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 9:24 Robert P. J. Day
2007-07-18 20:18 ` Jiri Slaby
2007-07-18 20:33 ` Robert P. J. Day
2007-07-18 22:38 ` Karel Zak [this message]
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=20070718223820.GF3181@petra.dvoda.cz \
--to=kzak@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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®