From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Chuck Luciano <chuck@mrluciano.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: My own 3.5G patch plus question on Ingo's 4G/$G patch
Date: Thu, 10 Jul 2003 13:20:12 -0700 [thread overview]
Message-ID: <810600000.1057868412@flay> (raw)
In-Reply-To: <NFBBKNADOLMJPCENHEALKEAHGBAA.chuck@mrluciano.com>
> On the subject of the 4G/4G patch, I started with 2.5.74, added
> patch-2.5.74-bk1 and http://redhat.com/~mingo/4g-patches/4g-2.5.74-F8
> and I get a hunk that fails:
>
> patching file include/asm-i386/mmu_context.h
> Hunk #1 FAILED at 29.
> Hunk #2 succeeded at 38 (offset -5 lines).
> Hunk #4 FAILED at 75.
> 2 out of 4 hunks FAILED -- saving rejects to file include/asm-i386/mmu_context.h.rej
>
> Is/are there a patch(es) that I'm missing?
Put it on top of the -bk6 snapshot.
M.
next prev parent reply other threads:[~2003-07-10 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 19:09 My own 3.5G patch plus question on Ingo's 4G/$G patch Chuck Luciano
2003-07-10 20:20 ` Martin J. Bligh [this message]
2003-07-10 20:56 ` Chuck Luciano
2003-07-10 23:02 ` Dave Hansen
2003-07-10 23:24 ` My own 3.5G patch - there was a bug in the patch I started with Chuck Luciano
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=810600000.1057868412@flay \
--to=mbligh@aracnet.com \
--cc=chuck@mrluciano.com \
--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