From: Jurriaan <thunder7@xs4all.nl>
To: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
Cc: Rafal Cichosz <rafal.cichosz@pt.onet.pl>, linux-kernel@vger.kernel.org
Subject: Re: ACPI APIC ERROR KT400 IRQ
Date: Mon, 23 Jun 2003 07:21:34 +0200 [thread overview]
Message-ID: <20030623052134.GA6085@middle.of.nowhere> (raw)
In-Reply-To: <1056322193.3557.10.camel@rousalka.dyndns.org>
From: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
Date: Mon, Jun 23, 2003 at 12:49:54AM +0200
> See
>
> http://bugzilla.kernel.org/show_bug.cgi?id=10
>
> and
>
> http://bugzilla.kernel.org/show_bug.cgi?id=71
>
> I believe 2.4 and 2.5 (mis)behaviour is now the same.
>
Hey, I know that one. Bug 678 is very similar :-)
Jurriaan
--
My sources tell me that you combine arrogance with trivia and try to
pass it off as intelligence.
Dogbert
Debian (Unstable) GNU/Linux 2.5.72 4112 bogomips load av: 1.93 1.39 1.10
next prev parent reply other threads:[~2003-06-23 5:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 22:49 ACPI APIC ERROR KT400 IRQ Nicolas Mailhot
2003-06-23 5:21 ` Jurriaan [this message]
2003-06-23 6:29 ` Nicolas Mailhot
-- strict thread matches above, loose matches on Subject: below --
2003-06-22 21:38 Rafal Cichosz
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=20030623052134.GA6085@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=Nicolas.Mailhot@laPoste.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rafal.cichosz@pt.onet.pl \
/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