path: root/README
diff options
authorKurt Wall <>2005-07-27 11:45:20 -0700
committerLinus Torvalds <>2005-07-27 16:26:09 -0700
commit896e5518da74f9d20db8163526014fba16b1f2b4 (patch)
treea3e333c22397665b6a87acd393071807f2f74beb /README
parente5c2d749172657ed51e20e4b5ab540447666cc50 (diff)
[PATCH] Add text for dealing with "dot releases" to README
The emergence of so-called "dot releases" that are non-incremental patches against a base kernel requires different handling of patches (revert previous patches before applying the newest one). This patch adds a paragrach to $TOPDIR/README explaining how to do deal with dot release patches. Signed-off-by: Kurt Wall <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
Diffstat (limited to 'README')
1 files changed, 10 insertions, 0 deletions
diff --git a/README b/README
index 0df20f0..76dd780 100644
--- a/README
+++ b/README
@@ -87,6 +87,16 @@ INSTALLING the kernel:
kernel source. Patches are applied from the current directory, but
an alternative directory can be specified as the second argument.
+ - If you are upgrading between releases using the stable series patches
+ (for example, patch-2.6.xx.y), note that these "dot-releases" are
+ not incremental and must be applied to the 2.6.xx base tree. For
+ example, if your base kernel is 2.6.12 and you want to apply the
+ patch, you do not and indeed must not first apply the
+ and patches. Similarly, if you are running kernel
+ version and want to jump to, you must first
+ reverse the patch (that is, patch -R) _before_ applying
+ the patch.
- Make sure you have no stale .o files and dependencies lying around:
cd linux
OpenPOWER on IntegriCloud