From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Rob van Nieuwkerk <robn@verdi.et.tudelft.nl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
"Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: 2.4.22-rc1 FIFO bug still present
Date: 08 Aug 2003 13:39:44 +0100 [thread overview]
Message-ID: <1060346384.4933.34.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030806192306.6085b3e0.robn@verdi.et.tudelft.nl>
On Mer, 2003-08-06 at 18:23, Rob van Nieuwkerk wrote:
> Stephen C. Tweedie made a fix (see below) for it in May.
> It has been in the Alan's -ac series since then and it works fine.
Certainly seems to be fine and it is a real bug. There is another unfixed
one of the same form with tty drivers too
next prev parent reply other threads:[~2003-08-08 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 17:23 2.4.22-rc1 FIFO bug still present Rob van Nieuwkerk
2003-08-08 12:39 ` Alan Cox [this message]
2003-08-08 12:54 ` Rob van Nieuwkerk
2003-08-08 17:23 ` Alan Cox
2003-08-08 14:46 ` Marcelo Tosatti
2003-08-07 16:51 Bartlomiej Zolnierkiewicz
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=1060346384.4933.34.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=robn@verdi.et.tudelft.nl \
--cc=sct@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).