From: "K.R. Foley" <kr@cybsft.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.16-rt24 Won't Apply
Date: Fri, 26 May 2006 14:04:09 -0500 [thread overview]
Message-ID: <44775129.6030004@cybsft.com> (raw)
Ingo,
The 2.6.16-rt24 patch that you uploaded today will not apply cleanly to
a 2.6.16 source tree. Below is the first of many problems, if this helps.
patching file Documentation/DocBook/Makefile
patching file Documentation/RCU/whatisRCU.txt
patching file Documentation/feature-removal-schedule.txt
patching file Documentation/kernel-parameters.txt
can't find file to patch at input line 96
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: linux/Documentation/robust-futexes.txt
|===================================================================
|--- linux.orig/Documentation/robust-futexes.txt
|+++ linux/Documentation/robust-futexes.txt
--------------------------
File to patch:
--
kr
next reply other threads:[~2006-05-26 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 19:04 K.R. Foley [this message]
2006-05-26 19:43 ` 2.6.16-rt24 Won't Apply Ingo Molnar
2006-05-26 20:04 ` K.R. Foley
2006-05-26 22:11 ` Mark Knecht
2006-05-26 22:32 ` Steven Rostedt
2006-05-26 23:52 ` Mark Knecht
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=44775129.6030004@cybsft.com \
--to=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.