From: Andrew Morton <akpm@osdl.org>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH: tty ldisc work version 4
Date: Wed, 22 Sep 2004 17:21:39 -0700 [thread overview]
Message-ID: <20040922172139.0d7a1dd3.akpm@osdl.org> (raw)
In-Reply-To: <20040922141821.GA27672@devserv.devel.redhat.com>
Alan Cox <alan@redhat.com> wrote:
>
> New features this time
> - Fix synclink layers - Paul Fulghum
> - Use tty_wakeup internally to tty_io
> - Add initial termios locking
> - Add ldisc hangup method for notification at hangup()
> - Fixed close to wait for running driver side events
>
> The big changes this time are locking/ordering rules for termios changes. As
> well as various feature changes I've also begun commenting n_tty.c so we
> can start tackling the ldisc internal issues.
This gives me "init_dev but no ldisc" when initscripts start playing with
the USB keyboard. The machine then stops.
next parent reply other threads:[~2004-09-23 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040922141821.GA27672@devserv.devel.redhat.com>
2004-09-23 0:21 ` Andrew Morton [this message]
2004-09-23 5:48 ` PATCH: tty ldisc work version 4 Alan Cox
2004-09-24 13:43 ` Paul Fulghum
2004-09-24 13:04 ` 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=20040922172139.0d7a1dd3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=alan@redhat.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