From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: bmckinlay@perle.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 60/80] tty: extract the pty init time special cases
Date: Wed, 28 Jan 2009 20:47:05 +0000 [thread overview]
Message-ID: <20090128204705.7140d5fd@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <OF7AEEC39E.E1555596-ON8525754C.006E408A-8525754C.0071A192@perle.com>
> So you are saying that if I merge my ptyx module into the kernel tree THEN
> these
> exports would be added? They would have to be, since I would still want
It would then seem reasonable to do so
> my
> driver to be a module instead of statically linked with the kernel like
> pty is.
Sure - although it might make more sense to add any neede features to the
generic pty driver - hard to tell when you don't seem interested in
discussing that.
> I think the fact that you had to "ask at the time what other PTY drivers
> there
> were" indicates that these symbols should have been simply exported to
> avoid
> any problems with out of tree PTY drivers.
The linux kernel doesn't carry extra symbols for out of tree drivers. Why
should it - even keeping an index of them would be hard and it would be
impossible to know which ones are in use. Plus they change regularly -
the tty layer will change further soon for example, it's just having a
settling in period before the next big changes.
> By not exporting these symbols it means that the Linux kernel is now
> forcing
> anyone who wants to develop a PTY type TTY driver to be merged into the
> kernel
> tree by not exporting these TTY functions. This doesn't seem very "open
> and
> flexible".
No you can provide the GPL symbol exports with the same patch as your pty
driver. There are millions of Linux users and each unused EXPORT_SYMBOL
costs memory to all those people - why should they carry that burden ?
Alan
next prev parent reply other threads:[~2009-01-28 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 2:16 bmckinlay
2009-01-22 12:40 ` Alan Cox
2009-01-28 20:36 ` bmckinlay
2009-01-28 20:47 ` Alan Cox [this message]
2009-01-29 18:30 ` bmckinlay
2009-01-29 19:34 ` Alan Cox
2009-02-02 15:42 ` bmckinlay
-- strict thread matches above, loose matches on Subject: below --
2008-10-13 9:31 [PATCH 00/80] TTY updates for 2.6.28 Alan Cox
2008-10-13 9:42 ` [PATCH 60/80] tty: extract the pty init time special cases Alan Cox
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=20090128204705.7140d5fd@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bmckinlay@perle.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®