From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "kees" <kees@schoen.nl>, <linux-kernel@vger.kernel.org>,
"Jonathan Lundell" <jlundell@pobox.com>, <tytso@mit.edu>
Subject: Re: Q serial.c
Date: Fri, 22 Jun 2001 11:32:06 -0400 [thread overview]
Message-ID: <07e401c0fb30$7eedf5a0$294b82ce@connecttech.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0106220846150.11538-100000@schoen3.schoen.nl> <070001c0fb22$69d68460$294b82ce@connecttech.com> <p05100303b759128e0e65@[207.213.214.37]>
From: "Jonathan Lundell" <jlundell@pobox.com>
> The other CPU servicing the interrupt, was the question. cli()
> doesn't affect that. This could presumably happen if shutdown() gets
> run on a non-interrupt-servicing CPU, or if interrupts are
> dynamically routed (eg round-robin).
Ah. Missed that.
Hm. Does appear to be a problem. Ted?
> Where can I find the 5.05 driver?
http://serial.sourceforge.net I'm not sure which version is currently
in 2.4.latest, but it should be nearly 5.05.
..Stu
prev parent reply other threads:[~2001-06-22 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 6:49 Q serial.c kees
2001-06-22 13:51 ` Stuart MacDonald
2001-06-22 15:23 ` Jonathan Lundell
2001-06-22 15:32 ` Stuart MacDonald [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='07e401c0fb30$7eedf5a0$294b82ce@connecttech.com' \
--to=stuartm@connecttech.com \
--cc=jlundell@pobox.com \
--cc=kees@schoen.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.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