From: Orion Poplawski <orion@cora.nwra.com>
To: linux-kernel@vger.kernel.org
Subject: Cannot apply sched-threading-2.4.21-E1 to 2.4.21 kernel
Date: Mon, 23 Jun 2003 10:06:41 -0600 [thread overview]
Message-ID: <bd78i4$iom$1@main.gmane.org> (raw)
I assumed that the scheduler patch sched-threading-2.4.21-E1 at
http://people.redhat.com/mingo/O(1)-scheduler/ is designed to be applied
to the 2.4.21 kernel? I'm not having any luck:
[root@earth linux-2.4.21]# patch -p1 < ../sched-threading-2.4.21-E1.patch
patching file fs/proc/array.c
Hunk #4 FAILED at 343.
Hunk #5 FAILED at 392.
2 out of 5 hunks FAILED -- saving rejects to file fs/proc/array.c.rej
patching file fs/proc/base.c
patching file fs/proc/inode.c
patching file fs/proc/proc_misc.c
Hunk #1 FAILED at 376.
1 out of 1 hunk FAILED -- saving rejects to file fs/proc/proc_misc.c.rej
patching file fs/smbfs/sock.c
patching file fs/ncpfs/sock.c
patching file fs/autofs/waitq.c
patching file fs/lockd/clntlock.c
patching file fs/lockd/clntproc.c
patching file fs/lockd/svc.c
patching file fs/nfsd/export.c
patching file fs/nfsd/nfssvc.c
patching file fs/jffs/intrep.c
patching file fs/autofs4/waitq.c
patching file fs/reiserfs/journal.c
patching file fs/jffs2/background.c
Hunk #1 succeeded at 110 with fuzz 1 (offset 3 lines).
Hunk #3 succeeded at 161 (offset 3 lines).
patching file fs/jfs/jfs_logmgr.c
patching file fs/jfs/jfs_txnmgr.c
patching file fs/jbd/journal.c
patching file fs/binfmt_aout.c
patching file fs/binfmt_elf.c
Hunk #4 succeeded at 602 (offset 3 lines).
Hunk #5 succeeded at 956 (offset -1 lines).
Hunk #6 succeeded at 986 (offset 3 lines).
Hunk #7 succeeded at 1004 (offset -1 lines).
Hunk #8 succeeded at 1175 (offset 3 lines).
Hunk #9 FAILED at 1222.
Hunk #10 succeeded at 1321 (offset -1 lines).
Hunk #11 succeeded at 1358 (offset 3 lines).
Hunk #12 succeeded at 1408 (offset -1 lines).
Hunk #13 succeeded at 1450 (offset 3 lines).
1 out of 13 hunks FAILED -- saving rejects to file fs/binfmt_elf.c.rej
patching file fs/buffer.c
Hunk #1 succeeded at 2920 (offset -41 lines).
Hunk #3 succeeded at 2995 (offset -41 lines).
patching file fs/exec.c
Hunk #2 succeeded at 465 (offset -7 lines).
Hunk #4 succeeded at 716 (offset -7 lines).
Hunk #6 succeeded at 839 (offset -7 lines).
Hunk #8 FAILED at 1247.
Hunk #9 succeeded at 1273 with fuzz 2 (offset -12 lines).
1 out of 9 hunks FAILED -- saving rejects to file fs/exec.c.rej
....and so on.
Was this a mistaken assumption?
reply other threads:[~2003-06-23 15:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='bd78i4$iom$1@main.gmane.org' \
--to=orion@cora.nwra.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 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.