diff options
author | Tom Rini <trini@ti.com> | 2013-04-19 19:03:27 (GMT) |
---|---|---|
committer | Tom Rini <trini@ti.com> | 2013-04-19 19:03:27 (GMT) |
commit | 79cd2f814b1c75efd47161ac27f4cbebf768240f (patch) | |
tree | 8ac6b609f4d87efe2cf3ca86ae3e59ae09ff232e /doc | |
parent | d10f68ae47b67acab8b110b5c605dde4197a1820 (diff) | |
download | u-boot-79cd2f814b1c75efd47161ac27f4cbebf768240f.tar.xz |
config_cmd_default.h: Remove CONFIG_CMD_MEMTEST
As per doc/feature-removal-schedule.txt, remove CONFIG_CMD_MEMTEST from
default list of commands.
Signed-off-by: Tom Rini <trini@ti.com>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/feature-removal-schedule.txt | 17 |
1 files changed, 0 insertions, 17 deletions
diff --git a/doc/feature-removal-schedule.txt b/doc/feature-removal-schedule.txt index ce72861..b4899c4 100644 --- a/doc/feature-removal-schedule.txt +++ b/doc/feature-removal-schedule.txt @@ -7,23 +7,6 @@ file. --------------------------- -What: Remove CONFIG_CMD_MEMTEST from default list -When: Release v2013.07 - -Why: The "mtest" command is of little practical use (if any), and - experience has shown that a large number of board configu- - rations define useless or even dangerous start and end - addresses. If not even the board maintainers are able to - figure out which memory range can be reliably tested, how can - we expect such from the end users? As this problem comes up - repeatedly, we rather do not enable this command by default, - so only people who know what they are doing will be confronted - with it. - -Who: Wolfgang Denk <wd@denx.de> - ---------------------------- - What: Remove CONFIG_SYS_ENABLE_PADS_ALL and CONFIG_SYS_CLOCKS_ENABLE_ALL When: Release v2013.07 |