From: Mike Fedyk <mfedyk@matchmail.com>
To: William Lee Irwin III <wli@holomorphy.com>,
Robert Love <rml@tech9.net>, Robert Jameson <rj@open-net.org>,
linux-kernel@vger.kernel.org
Subject: Re: Hard lockup with 2.4.18-pre9 + preempt + lock break + O1k[23] + rmap
Date: Fri, 15 Feb 2002 15:42:25 -0800 [thread overview]
Message-ID: <20020215234225.GC5310@matchmail.com> (raw)
In-Reply-To: <20020215035135.0c26b130.rj@open-net.org> <1013780277.950.663.camel@phantasy> <20020215201810.GA5310@matchmail.com> <1013810411.803.1045.camel@phantasy> <20020215232221.GB5310@matchmail.com> <20020215233040.GA782@holomorphy.com>
In-Reply-To: <20020215233040.GA782@holomorphy.com>
On Fri, Feb 15, 2002 at 03:30:40PM -0800, William Lee Irwin III wrote:
> On Fri, Feb 15, 2002 at 03:22:21PM -0800, Mike Fedyk wrote:
> > Yep, I understand. When I was patching in rmap12f I had to manually
> > merge the little bit into mm/bootmem.c and the offset was several hundred
> > lines. Then I realized just how much WLI's bootmem patch changes.
>
> It's a rewrite. Of course it changes the whole file. Lucky for you it
> interacts with nothing else. I seem to remember this conflict being
> somewhat trivial to resolve though.
Yes, it was quite easy to hand merge/fix it up when I added in rmap12f (was
12e... so not much to change.)
Mike
next prev parent reply other threads:[~2002-02-15 23:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 8:51 oops with 2.4.18-pre9-mjc2 Robert Jameson
2002-02-15 8:55 ` William Lee Irwin III
2002-02-15 13:29 ` Michael Cohen
2002-02-15 13:37 ` Robert Love
2002-02-15 15:20 ` Robert Jameson
2002-02-15 15:30 ` Arjan van de Ven
2002-02-15 17:48 ` Alan Cox
2002-02-15 19:15 ` Robert Love
2002-02-15 20:18 ` Hard lockup with 2.4.18-pre9 + preempt + lock break + O1k[23] + rmap Mike Fedyk
2002-02-15 22:00 ` Robert Love
2002-02-15 23:22 ` Mike Fedyk
2002-02-15 23:30 ` William Lee Irwin III
2002-02-15 23:42 ` Mike Fedyk [this message]
2002-02-16 9:29 ` Zwane Mwaikambo
2002-02-15 14:26 ` oops with 2.4.18-pre9-mjc2 Alan Cox
2002-02-15 16:07 ` Greg KH
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=20020215234225.GC5310@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rj@open-net.org \
--cc=rml@tech9.net \
--cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox