From: viro@parcelfarce.linux.theplanet.co.uk
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: [RFC][TTY] callout removal
Date: Tue, 13 May 2003 07:23:32 +0100 [thread overview]
Message-ID: <20030513062332.GW10374@parcelfarce.linux.theplanet.co.uk> (raw)
Folks, it had been quite a few years since callout tty devices had
been deprecated. IMO it's time to bury them - the following
if ((tty->driver.type == TTY_DRIVER_TYPE_SERIAL) &&
(tty->driver.subtype == SERIAL_TYPE_CALLOUT)) {
printk("Warning, %s opened, is a deprecated tty "
"callout device\n", tty_name(tty, buf));
in tty_open() had been theres since 2.1.90-pre2. IOW, we had two stable
branches since then.
Quite a few things in tty code and related data structures exist only
because of these beasts and I'd rather get rid of them.
If nobody has serious objections I'll submit patches removing that stuff,
so if you _do_ have a reason to keep callouts around, yell now.
next reply other threads:[~2003-05-13 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 6:23 viro [this message]
2003-05-13 6:44 ` [RFC][TTY] callout removal Andrew Morton
2003-05-13 7:04 ` Matti Aarnio
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=20030513062332.GW10374@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).