diff options
| author |   Kees Cook <keescook@chromium.org> | 2012-10-02 11:16:15 -0700 |
|---|---|---|
| committer | Kees Cook <keescook@chromium.org> | 2013-01-11 11:38:03 -0800 |
| commit | 0335cb469ad4ab3072a4246ceb0573483fcee5bf (patch) | |
| tree | 9dddc1aecd4a51820e293e57c6798a734ef640cd /Documentation/DocBook/kernel-hacking.tmpl | |
| parent | make CONFIG_EXPERIMENTAL invisible and default (diff) | |
| download | linux-dev-0335cb469ad4ab3072a4246ceb0573483fcee5bf.tar.xz linux-dev-0335cb469ad4ab3072a4246ceb0573483fcee5bf.zip | |
Documentation: remove depends on CONFIG_EXPERIMENTAL
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Rob Landley <rob@landley.net>
CC: Jiri Kosina <jkosina@suse.cz>
CC: Masanari Iida <standby24x7@gmail.com>
CC: Jason Wessel <jason.wessel@windriver.com>
CC: Richard L Maliszewski <richard.l.maliszewski@intel.com>
CC: Gang Wei <gang.wei@intel.com>
CC: Shane Wang <shane.wang@intel.com>
CC: Harry Wei <harryxiyou@gmail.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Jason Wessel <jason.wessel@windriver.com>
Diffstat (limited to 'Documentation/DocBook/kernel-hacking.tmpl')
| -rw-r--r-- | Documentation/DocBook/kernel-hacking.tmpl | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/Documentation/DocBook/kernel-hacking.tmpl b/Documentation/DocBook/kernel-hacking.tmpl index eee71426ecb8..22e0bd1adf25 100644 --- a/Documentation/DocBook/kernel-hacking.tmpl +++ b/Documentation/DocBook/kernel-hacking.tmpl @@ -1185,13 +1185,6 @@ static struct block_device_operations opt_fops = { </para> <para> - You may well want to make your CONFIG option only visible if - <symbol>CONFIG_EXPERIMENTAL</symbol> is enabled: this serves as a - warning to users. There many other fancy things you can do: see - the various <filename>Kconfig</filename> files for ideas. - </para> - - <para> In your description of the option, make sure you address both the expert user and the user who knows nothing about your feature. Mention incompatibilities and issues here. <emphasis> Definitely |