From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH RFC]: New termios take 2
Date: Sun, 10 Sep 2006 14:06:29 +0100 [thread overview]
Message-ID: <1157893589.2977.162.camel@pmac.infradead.org> (raw)
In-Reply-To: <1157891081.23085.1.camel@localhost.localdomain>
On Sun, 2006-09-10 at 13:24 +0100, Alan Cox wrote:
> glibc needs them, nobody else does.
>
> The point I was trying to make is that user space (except glibc) does
> not use them. glibc presents a different struct termios to them already,
> and it always includes c_ispeed/c_ospeed.
That's not the point. The question is what glibc's _implementation_ uses
for doing the ioctls. It has to have _some_ definition of the kernel's
version of the structure.
In fact it seems to have its own 'kernel_termios.h' which is an old copy
of our headers. So in that case, we really can drop <asm/termios.h> from
the export -- as least as far as glibc is concerned. I'm not sure about
other C libraries.
On the other hand, the kind of change you're making is an example of why
we might want glibc to be using a _sanely_ exported copy of our headers
directly, rather than an out-of-date version of its own. But that's a
policy decision I'll leave to you.
If you want to declare that asm/termios.h isn't to be exported even for
glibc builds then please drop all __KERNEL__ from it and remove it from
include/asm-generic/Kbuild.asm so that it isn't exported.
--
dwmw2
next prev parent reply other threads:[~2006-09-10 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 16:14 Alan Cox
2006-09-10 10:46 ` David Woodhouse
2006-09-10 11:15 ` Alan Cox
2006-09-10 11:20 ` David Woodhouse
2006-09-10 12:24 ` Alan Cox
2006-09-10 13:06 ` David Woodhouse [this message]
2006-09-10 22:19 ` Arnd Bergmann
2006-09-11 10:13 ` David Howells
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=1157893589.2977.162.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-arch@vger.kernel.org \
--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®