From: Ian Kumlien <pomac@vapor.com>
To: a.verweij@student.tudelft.nl
Cc: Ross Dickson <ross@datscreative.com.au>,
cbradney@zip.com.au, linux-kernel@vger.kernel.org,
Len Brown <len.brown@intel.com>,
"Prakash K. Cheemplavam" <PrakashKC@gmx.de>,
christian.kroener@tu-harburg.de,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Jamie Lokier <jamie@shareable.org>,
Daniel Drake <dan@reactivated.net>,
Allen Martin <AMartin@nvidia.com>
Subject: Re: IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH]
Date: Mon, 10 May 2004 19:39:58 +0200 [thread overview]
Message-ID: <1084210798.2954.12.camel@big> (raw)
In-Reply-To: <Pine.GHP.4.44.0405101659320.6908-100000@elektron.its.tudelft.nl>
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
On Mon, 2004-05-10 at 17:05, Arjen Verweij wrote:
> Does the 2.6.6 Changelog section about nforce2 imply that Ross' Patches of
> Stability are no longer required? I don't read lkml regularely, so this
> would be new for me.
>
> Anyway, if this works (tm) I am very happy. Will attempt to test it later
> on, even though I have Maxtor 8MB discs :)
Sorry, i must have needed food or so, i missed the post you had there...
=P
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-10 17:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 11:37 IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] Ross Dickson
2004-05-10 12:07 ` Craig Bradney
2004-05-10 12:22 ` Ian Kumlien
2004-05-10 15:05 ` Arjen Verweij
2004-05-10 16:04 ` Ian Kumlien
2004-05-10 17:39 ` Ian Kumlien [this message]
2004-05-24 16:10 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2004-05-07 7:29 Ian Kumlien
2004-05-08 3:45 ` Richard James
2004-05-08 5:31 ` Richard James
2004-05-08 9:22 ` Ian Kumlien
2004-05-10 8:49 ` Craig Bradney
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=1084210798.2954.12.camel@big \
--to=pomac@vapor.com \
--cc=AMartin@nvidia.com \
--cc=PrakashKC@gmx.de \
--cc=a.verweij@student.tudelft.nl \
--cc=cbradney@zip.com.au \
--cc=christian.kroener@tu-harburg.de \
--cc=dan@reactivated.net \
--cc=jamie@shareable.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=ross@datscreative.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.