From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: eric.valette@free.fr,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-rc1 : aic7xxx deadlock on boot on my machine
Date: 22 Apr 2003 15:11:33 +0100 [thread overview]
Message-ID: <1051020692.14881.12.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <200304221036.19274.m.c.p@wolk-project.de>
On Maw, 2003-04-22 at 09:36, Marc-Christian Petersen wrote:
> > So I hope, it will be updated in rc2...
> I'll _bet_ that the new well good code from Justin won't make it into 2.4
> earlier than 2.4.22-pre1.
Its not the good code that worries me - its what bits of it turn out to
be buggy
next prev parent reply other threads:[~2003-04-22 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 8:37 Linux 2.4.21-rc1 : aic7xxx deadlock on boot on my machine Eric Valette
2003-04-22 8:36 ` Marc-Christian Petersen
2003-04-22 8:53 ` Eric Valette
2003-04-22 14:11 ` Alan Cox [this message]
2003-04-22 19:34 ` Eric Valette
2003-04-22 22:15 ` Alan Cox
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=1051020692.14881.12.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=eric.valette@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
/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).