From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Paul Fulghum <paulkf@microgate.com>
Cc: Alan Cox <alan@redhat.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: tty ldisc work version 4
Date: Fri, 24 Sep 2004 14:04:31 +0100 [thread overview]
Message-ID: <1096031067.9730.21.camel@localhost.localdomain> (raw)
In-Reply-To: <1096033380.4995.6.camel@deimos.microgate.com>
On Gwe, 2004-09-24 at 14:43, Paul Fulghum wrote:
> Did this turn out to be related to the code
> in release_dev() that switches back a tty struct
> back to N_TTY ldisc before freeing the tty struct?
No it was just a stupid mistake in my code. I'll propogate the
other changes back in now I've found it.
prev parent reply other threads:[~2004-09-24 14:07 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 ` PATCH: tty ldisc work version 4 Andrew Morton
2004-09-23 5:48 ` Alan Cox
2004-09-24 13:43 ` Paul Fulghum
2004-09-24 13:04 ` Alan Cox [this message]
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=1096031067.9730.21.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.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