Gentoo Archives: gentoo-user

From: Mark Knecht <markknecht@×××××.com>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Adding realtime-prempt kernel patches to gentoo-sources
Date: Thu, 07 Jul 2005 17:54:30
Message-Id: 5bdc1c8b05070710451075bdd5@mail.gmail.com
1 Hi,
2 I'm interested in using Ingo Molnar's realtime-preempt kernel
3 patches with a Gentoo kernel. I already use them with a Kernel.org
4 kernel but would prefer to one day see these be part of what Gentoo
5 supplies. This morning I did a --dry-run and see some messages like
6 this:
7
8 patching file Makefile
9 Hunk #1 FAILED at 1.
10 1 out of 2 hunks FAILED -- saving rejects to file Makefile.rej
11 patching file arch/arm/mach-pxa/corgi_ssp.c
12 patching file arch/i386/Kconfig
13 <SNIP>
14 patching file arch/mips/Kconfig
15 Hunk #3 succeeded at 907 (offset 2 lines).
16 Hunk #4 succeeded at 942 (offset 2 lines).
17 Hunk #5 succeeded at 1469 (offset 2 lines).
18 Hunk #6 succeeded at 1483 (offset 2 lines).
19 patching file arch/mips/kernel/Makefile
20 <SNIP>
21 patching file drivers/video/console/fbcon.c
22 Hunk #1 succeeded at 1063 (offset 11 lines).
23 Hunk #2 FAILED at 1091.
24 Hunk #3 succeeded at 2874 (offset 106 lines).
25 1 out of 3 hunks FAILED -- saving rejects to file
26 drivers/video/console/fbcon.c.rej
27 patching file drivers/video/console/vgacon.c
28
29
30 QUESTIONS:
31
32 1) Can I assume that whatever happened with the "Hunk #x succeeded"
33 that everything is OK? Maybe this was just a line number issue?
34
35 2) What can I do about the "Hunk #x FAILED" messages?
36
37 No output files were created since it was only a dry run. I can run
38 again, get output files, and then look into it but I thought I'd ask
39 how folks go about this sort of thing before I pulled the trigger.
40
41 Thanks,
42 Mark
43
44 --
45 gentoo-user@g.o mailing list

Replies

Subject Author
Re: [gentoo-user] Adding realtime-prempt kernel patches to gentoo-sources Christian Heim <christian.th.heim@×××.de>