dts: zynq: Add zynq spi controller nodes

[karo-tx-uboot.git] / doc / feature-removal-schedule.txt

diff --git a/doc/feature-removal-schedule.txt b/doc/feature-removal-schedule.txt
index d9a0cc267beaa1029b3403fb19654cc33cc3855e..4ed30df707ecd8f32b1e62d60c98cf695378efd3 100644 (file)
--- a/doc/feature-removal-schedule.txt
+++ b/doc/feature-removal-schedule.txt
@@ -7,20 +7,15 @@ file.
 
 ---------------------------
 
 
 ---------------------------
 

-What:  Remove CONFIG_CMD_MEMTEST from default list
-When:  Release v2013.07
+What:  Remove unused CONFIG_SYS_MEMTEST_START/END
+When:  Release v2013.10

 
 

-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.
+Why:   As the 'mtest' command is no longer default, a number of platforms
+       have not opted to turn the command back on and thus provide unused
+       defines (which are likely to be propogated to new platforms from
+       copy/paste).  Remove these defines when unused.

 
 

-Who:   Wolfgang Denk <wd@denx.de>
+Who:   Tom Rini <trini@ti.com>

 
 ---------------------------
 
 
 ---------------------------
 


@@ -31,23 +26,7 @@ Why: We now have a PHY library, which allows everyone to share PHY
        drivers. All new drivers should use this infrastructure, and
        all old drivers should get converted to use it.
 
        drivers. All new drivers should use this infrastructure, and
        all old drivers should get converted to use it.
 

-Who:   Andy Fleming <afleming@freescale.com> and driver maintainers
-
----------------------------
-
-What:  boards with xxx_config targets in top level Makefile
-When:  Release v2012.03
-
-Why:   We have a boards.cfg file which the vast majority of boards have
-       converted over to.  Boards that still manually run mkconfig in the
-       top level Makefile are either dead, or the maintainer doesn't care,
-       or they are doing something weird/wrong that should be fixed in a
-       different way, or they need to extend boards.cfg syntax (unlikely).
-
-       In any case, if no one cares about these boards to figure out how
-       to make boards.cfg work, then we'll just punt them.
-
-Who:   Mike Frysinger <vapier@gentoo.org>
+Who:   Andy Fleming <afleming@gmail.com> and driver maintainers

 
 ---------------------------
 
 
 ---------------------------