diff options
author | Luis R. Rodriguez <mcgrof@suse.com> | 2014-11-04 18:14:29 -0800 |
---|---|---|
committer | Luis R. Rodriguez <mcgrof@do-not-panic.com> | 2014-11-14 13:47:17 -0800 |
commit | 1ce22a0938ac10c576431fc1d3150763f15aa4d8 (patch) | |
tree | bcbe6af244d21924149273bc672851daab7cc012 /devel | |
parent | cb1b116353ad544dd8238edbe71efcca838b001a (diff) |
backports: remove extra BACKPORT_ prefix from kernel versioning
The CPTCFG_ prefix already implies backport, when integration
is used we'd end up with a double BACKPORT_ prefix, so just
remove the existing one as its not needed.
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
Diffstat (limited to 'devel')
-rw-r--r-- | devel/doc/kconfig-operation | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/devel/doc/kconfig-operation b/devel/doc/kconfig-operation index f1ecf609..ddb4de77 100644 --- a/devel/doc/kconfig-operation +++ b/devel/doc/kconfig-operation @@ -53,12 +53,12 @@ The second file (Kconfig.versions) is generated from just the version of the kernel and also contains invisible and unselectable boolean options like -config BACKPORT_KERNEL_X +config KERNEL_X def_bool y to indicate that APIs introduced in kernel version X (e.g. 3_3 for 3.3 or 2_6_24 for 2.6.24) must be backported. Essentially, the presence of -a symbol BACKPORT_KERNEL_X indicates that the kernel that the code is +a symbol KERNEL_X indicates that the kernel that the code is being compiled against is older than X. All together, this allows the correct options to be selected by the user. @@ -121,7 +121,7 @@ These are the problems and their solutions: requires at least 2.6.29 due to the shash crypto code. This cannot be determined easily automatically, so the 'dependencies' file is read and options that are listed there are rewritten to include - depends on !BACKPORT_KERNEL_X_Y + depends on !KERNEL_X_Y (where X_Y is the listed kernel version), which makes them available only on kernels >= X.Y. |