All of lore.kernel.org
 help / color / mirror / Atom feed
From: "b@netzentry.com" <b@netzentry.com>
To: recbo@nishanet.com, linux-kernel@vger.kernel.org
Subject: RE: merged in bk5 Re: Catching NForce2 lockup with NMI watchdog - found?
Date: Tue, 09 Dec 2003 14:57:11 -0800	[thread overview]
Message-ID: <3FD65347.6060109@netzentry.com> (raw)

Is this stuff going to be merged into 2.4 soon? I'd like
to try a 2.4.23/24-bk with these patches.


 >From: Bob
 >Subject: merged in bk5 Re: Catching NForce2 lockup with NMI
 >
 >if you're following this thread, good news--
 >
 >nforce2 fixups have been merged in
 >linux-2.6.0-test11-bk5.patch
 >>  -bk snapshot (patch-2.6.0-test11-bk5)
 >
 >nforce2-disconnect-quirk.patch
 >>  [x86] fix lockups with APIC support on nForce2
 >>
 >>nforce2-apic.patch
 >>  [x86] do not wrongly override mp_ExtINT IRQ
 >
 >plus promise and sis fixes so I don't need to pay
 >for a 3ware controller ;-)   that was another
 >show-stopper for me earlier
 >
 >> We're all trying to get acpi, apic, lapic, io-apic working
 >> when turned on in cmos/bios and kernel.
 >>



             reply	other threads:[~2003-12-09 22:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 22:57 b [this message]
2003-12-10  0:51 ` merged in bk5 Re: Catching NForce2 lockup with NMI watchdog - found? Josh McKinney
2003-12-10  4:48 ` Bob
  -- strict thread matches above, loose matches on Subject: below --
2003-12-08  3:21 Ross Dickson
2003-12-08 11:36 ` Craig Bradney
2003-12-08 17:40 ` Bob
2003-12-09 16:44   ` merged in bk5 " Bob
2003-12-09 16:43     ` 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=3FD65347.6060109@netzentry.com \
    --to=b@netzentry.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=recbo@nishanet.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 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.