From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Adding realtime-prempt kernel patches to gentoo-sources
Date: Thu, 7 Jul 2005 10:45:12 -0700 [thread overview]
Message-ID: <5bdc1c8b05070710451075bdd5@mail.gmail.com> (raw)
Hi,
I'm interested in using Ingo Molnar's realtime-preempt kernel
patches with a Gentoo kernel. I already use them with a Kernel.org
kernel but would prefer to one day see these be part of what Gentoo
supplies. This morning I did a --dry-run and see some messages like
this:
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 2 hunks FAILED -- saving rejects to file Makefile.rej
patching file arch/arm/mach-pxa/corgi_ssp.c
patching file arch/i386/Kconfig
<SNIP>
patching file arch/mips/Kconfig
Hunk #3 succeeded at 907 (offset 2 lines).
Hunk #4 succeeded at 942 (offset 2 lines).
Hunk #5 succeeded at 1469 (offset 2 lines).
Hunk #6 succeeded at 1483 (offset 2 lines).
patching file arch/mips/kernel/Makefile
<SNIP>
patching file drivers/video/console/fbcon.c
Hunk #1 succeeded at 1063 (offset 11 lines).
Hunk #2 FAILED at 1091.
Hunk #3 succeeded at 2874 (offset 106 lines).
1 out of 3 hunks FAILED -- saving rejects to file
drivers/video/console/fbcon.c.rej
patching file drivers/video/console/vgacon.c
QUESTIONS:
1) Can I assume that whatever happened with the "Hunk #x succeeded"
that everything is OK? Maybe this was just a line number issue?
2) What can I do about the "Hunk #x FAILED" messages?
No output files were created since it was only a dry run. I can run
again, get output files, and then look into it but I thought I'd ask
how folks go about this sort of thing before I pulled the trigger.
Thanks,
Mark
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2005-07-07 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 17:45 Mark Knecht [this message]
2005-07-07 18:07 ` [gentoo-user] Adding realtime-prempt kernel patches to gentoo-sources Christian Heim
2005-07-07 20:09 ` Mark Knecht
2005-07-07 20:31 ` Christian Heim
2005-07-07 20:52 ` Mark Knecht
2005-07-07 21:45 ` Mark Knecht
2005-07-08 11:51 ` Christian Heim
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=5bdc1c8b05070710451075bdd5@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.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