From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "Val Henson" <val@nmt.edu>
Cc: "Theodore Tso" <tytso@valinux.com>,
<linux-kernel@vger.kernel.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] drivers/char/serial.c bug in ST16C654 detection
Date: Thu, 17 May 2001 09:49:11 -0400 [thread overview]
Message-ID: <043a01c0ded8$274f8940$294b82ce@connecttech.com> (raw)
In-Reply-To: <20010511182723.M18959@boardwalk> <033101c0dcaf$10557f40$294b82ce@connecttech.com> <20010514162010.G5060@boardwalk> <010001c0dd46$38fc9360$294b82ce@connecttech.com> <20010516161245.O6892@boardwalk>
From: "Val Henson" <val@nmt.edu>
> Anyone know where Ted Tso is? He hasn't posted in several weeks.
Haven't heard from him in a while. I've got a patch or two pending
as well, one of which modifies this code to check for 16c2850s.
Usually he just says he's really busy.
> > Kernel version? Distribution? Are you using a serial console?
> 2.4.5-pre1 (see patch).
Are you using the serial console though? That seems to be
implied by your problem, but I just want to check.
> Because the comment was ambiguous. I don't have the data sheet for
> the 85x family so I just wrote the code according to the comment.
> I'll change the comment to make it clear.
Hm. I didn't really read the comment, since I know what the
code is doing. :-) I can send you an 864 sheet if you'd like;
we most likely have the other 85x sheets around somewhere;
all pdf format.
..Stu
next prev parent reply other threads:[~2001-05-17 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-12 0:27 [PATCH] drivers/char/serial.c bug in ST16C654 detection Val Henson
2001-05-14 19:50 ` Stuart MacDonald
2001-05-14 22:20 ` Val Henson
2001-05-15 13:52 ` Stuart MacDonald
2001-05-16 22:12 ` Val Henson
2001-05-16 23:12 ` Theodore Tso
2001-05-17 13:49 ` Stuart MacDonald [this message]
2001-05-17 23:20 ` Val Henson
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='043a01c0ded8$274f8940$294b82ce@connecttech.com' \
--to=stuartm@connecttech.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@valinux.com \
--cc=val@nmt.edu \
/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