public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: arjan@fenrus.demon.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.10aa1 (00_vm-tweaks-1)
Date: Sun, 23 Sep 2001 23:49:55 +0200	[thread overview]
Message-ID: <20010923234955.F1782@athlon.random> (raw)
In-Reply-To: <20010923232511.B1466@athlon.random> <m15lGv2-000OVWC@amadeus.home.nl>
In-Reply-To: <m15lGv2-000OVWC@amadeus.home.nl>; from arjan@fenrus.demon.nl on Sun, Sep 23, 2001 at 10:36:08PM +0100

On Sun, Sep 23, 2001 at 10:36:08PM +0100, arjan@fenrus.demon.nl wrote:
> In article <20010923232511.B1466@athlon.random> you wrote:
> 
> > Only in 2.4.10aa1: 00_enable-apic-1
> 
> >        Enable UP ioapic on demand via boot param.
> 
> If you took my patch for it, PLEASE don't send it for inclusion; it's an
> evil hack and no longer needed when Intel fixes the bug in their 440GX bios.

we're having troubles with the ioapic compiled in in UP on some machine,
on 2.4.10pre I assume. Waiting bios updates is more problematic then
enabling on demand rather than disabling on demand, so yes I will be
obviously glad to drop this one as soon as the problem goes away.
thanks for the info.

Andrea

  parent reply	other threads:[~2001-09-23 21:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010923232511.B1466@athlon.random>
2001-09-23 21:36 ` 2.4.10aa1 (00_vm-tweaks-1) arjan
2001-09-23 21:46   ` Alan Cox
2001-09-23 21:46     ` arjan
2001-09-25  8:33       ` john slee
2001-09-25 17:53         ` Marcelo Tosatti
2001-09-25 18:44         ` Andrea Arcangeli
2001-09-23 21:50     ` Andrea Arcangeli
2001-09-23 21:49   ` Andrea Arcangeli [this message]
2001-09-24 16:51     ` Ingo Molnar
2001-09-24 13:42 ` Adrian Bunk
2001-09-25 18:49   ` Andrea Arcangeli
2001-09-27 13:29     ` Adrian Bunk

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=20010923234955.F1782@athlon.random \
    --to=andrea@suse.de \
    --cc=arjan@fenrus.demon.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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