From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: drivers/char/rocket.c: somewhat broken since 2.6.16
Date: Thu, 25 May 2006 12:18:29 +0100 [thread overview]
Message-ID: <1148555909.12482.33.camel@localhost.localdomain> (raw)
In-Reply-To: <44757A09.8060603@tls.msk.ru>
On Iau, 2006-05-25 at 13:34 +0400, Michael Tokarev wrote:
> I'm trying to use rocket.c from 2.6.15 on a 2.6.16 kernel now,
> let's see what will happen...
I imagine it'll break spectacularly as the tty layer handling changed
between the two quite a bit. Do you know if the modem is receving the
characters as you typed and the echo is delayed or vice versa.
I do have one patch for the rocket driver to fix an obscure Oops case
but nothing else. I'm also hoping to help find a way that works for
comtrol and the kernel folks to get a current comtrol driver into the
tree in a way that they can maintain easily.
Please stick the bug into the kernel bugzilla and assign it to me. I'll
do a bit of digging see what is up
prev parent reply other threads:[~2006-05-25 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 9:34 drivers/char/rocket.c: somewhat broken since 2.6.16 Michael Tokarev
2006-05-25 11:18 ` 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=1148555909.12482.33.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.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