aboutsummaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorDave Kleikamp <shaggy@austin.ibm.com>2005-07-28 10:03:36 -0400
committerDave Kleikamp <shaggy@austin.ibm.com>2005-07-28 10:03:36 -0400
commitda28c12089dfcfb8695b6b555cdb8e03dda2b690 (patch)
treeb3ff509f21352ef053cb3d490cb13528090d32ac /README
parent6de7dc2c4c713d037c19aa1e310d240f16973414 (diff)
parent577a4f8102d54b504cb22eb021b89e957e8df18f (diff)
Merge with /home/shaggy/git/linus-clean/
/home/shaggy/git/linus-clean/ /home/shaggy/git/linus-clean/ Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
Diffstat (limited to 'README')
-rw-r--r--README10
1 files changed, 10 insertions, 0 deletions
diff --git a/README b/README
index 0df20f07227b..76dd780d88ed 100644
--- a/README
+++ b/README
@@ -87,6 +87,16 @@ INSTALLING the kernel:
87 kernel source. Patches are applied from the current directory, but 87 kernel source. Patches are applied from the current directory, but
88 an alternative directory can be specified as the second argument. 88 an alternative directory can be specified as the second argument.
89 89
90 - If you are upgrading between releases using the stable series patches
91 (for example, patch-2.6.xx.y), note that these "dot-releases" are
92 not incremental and must be applied to the 2.6.xx base tree. For
93 example, if your base kernel is 2.6.12 and you want to apply the
94 2.6.12.3 patch, you do not and indeed must not first apply the
95 2.6.12.1 and 2.6.12.2 patches. Similarly, if you are running kernel
96 version 2.6.12.2 and want to jump to 2.6.12.3, you must first
97 reverse the 2.6.12.2 patch (that is, patch -R) _before_ applying
98 the 2.6.12.3 patch.
99
90 - Make sure you have no stale .o files and dependencies lying around: 100 - Make sure you have no stale .o files and dependencies lying around:
91 101
92 cd linux 102 cd linux