From: Stas Sergeev <stsp@aknet.ru>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: lockup when accessing serial port (and fix)
Date: Mon, 21 Feb 2005 20:41:50 +0300 [thread overview]
Message-ID: <421A1D5E.2040200@aknet.ru> (raw)
In-Reply-To: <20050221171228.A2768@flint.arm.linux.org.uk>
<><>
<><><>Hello.
Russell King wrote:
>> Known bug, just nobody has bothered to fix it. Please send the fix to
>> Linus so it gets into 2.6.11
> The fix was submitted to and accepted by Linus on Feb 8th. Therefore,
> there's nothing to "bother" with.
I've seen that fix in the latest -mm
patch released shortly after I wrote
the original message, but I can't help
feeling that the other serial drivers
have the same bug. I can see the very
same code in the au1x00_uart.c and other
files too, and it doesn't look like the
fix affected those.
I wasn't dare to ask, but now since also
Alan is bothered - can you please confirm
the other drivers are safe?
<>
<>
<>
prev parent reply other threads:[~2005-02-21 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 20:30 lockup when accessing serial port (and fix) Stas Sergeev
2005-02-21 15:03 ` Alan Cox
2005-02-21 17:12 ` Russell King
2005-02-21 17:41 ` Stas Sergeev [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=421A1D5E.2040200@aknet.ru \
--to=stsp@aknet.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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