From: Horms <horms@verge.net.au>
To: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Jason Baron <jbaron@redhat.com>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Sergey Vlasov <vsu@altlinux.ru>
Subject: Re: tty/ldisc fix in 2.4
Date: Fri, 17 Dec 2004 11:28:20 +0900 [thread overview]
Message-ID: <20041217022818.GA7844@verge.net.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0412161002520.28739-100000@dhcp83-105.boston.redhat.com>
On Thu, Dec 16, 2004 at 10:08:34AM -0500, Jason Baron wrote:
>
> On Thu, 16 Dec 2004, Marcelo Tosatti wrote:
>
> > On Thu, Dec 16, 2004 at 01:42:29PM +0900, Horms wrote:
> > > Hi,
> >
> > Hi Horms,
> >
> > > I am unable to find a fix for the tty/ldisc problem (CAN-2004-0814)
> > > in 2.4.28 or 2.4 bitkeeper. I am wondering if anyone can either
> > > point me to what I am missing or indicate if there is a reason
> > > the patch hasn't been included. e.g. it slipped through the cracks.
> >
> > The patch has not been included in 2.4.28 because it was too late in the
> > v2.4.28 cycle for them to be included - they are quite intrusive.
> >
> > And they there didnt seem stable at the time - but yes - we
> > should now make an effort to include the locking fixes in 2.4.29.
> >
> > > The last I can find of it is here:
> > > http://www.ussg.iu.edu/hypermail/linux/kernel/0410.3/1750.html
> >
> > Jason, can you point us at your last patch ?
> the latest one was the last one posted to this list plus Sergey's fixes.
> However, i think it was still missing some driver cleanups. I'll post an
> updated patch here.
Hi,
thanks to all for the update. This definately answers my question.
I will watch out for Jason's updated patch.
--
Horms
next prev parent reply other threads:[~2004-12-17 2:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 4:42 tty/ldisc fix in 2.4 Horms
2004-12-16 8:14 ` Marcelo Tosatti
2004-12-16 11:28 ` Sergey Vlasov
2004-12-16 15:08 ` Jason Baron
2004-12-17 2:28 ` Horms [this message]
2004-12-17 19:52 ` Jason Baron
2004-12-18 1:03 ` Marcelo Tosatti
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=20041217022818.GA7844@verge.net.au \
--to=horms@verge.net.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=vsu@altlinux.ru \
/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