Coding Style cleanup; update CHANGELOG, prepare -rc1v2009.11-rc1

Signed-off-by: Wolfgang Denk <wd@denx.de>

3 files changed, 12 insertions, 12 deletions

diff --git a/doc/README.bitbangMII b/doc/README.bitbangMII
index edd0856..0a2fa48 100644
--- a/doc/README.bitbangMII
+++ b/doc/README.bitbangMII
@@ -6,7 +6,7 @@ buses are implemented via bit-banging mode.
 The driver requires that the following macros should be defined into the board
 configuration file:
 
-CONFIG_BITBANGMII       - Enable the miiphybb driver
+CONFIG_BITBANGMII	- Enable the miiphybb driver
 CONFIG_BITBANGMII_MULTI - Enable the multi bus support
 
 If the CONFIG_BITBANGMII_MULTI is not defined, the board's config file needs
@@ -19,7 +19,7 @@ MDIO_TRISTATE - Activate the MDIO pin as input/tristate pin
 MDIO_READ     - Read the MDIO pin
 MDIO(v)       - Write v on the MDIO pin
 MDC_DECLARE   - Declaration needed to access to the MDC pin (optional)
-MDC(v)        - Write v on the MDC pin
+MDC(v)	      - Write v on the MDC pin
 
 The previous macros make the driver compatible with the previous version
 (that didn't support the multi-bus).
@@ -30,17 +30,17 @@ the bb_miiphy_buses_num variable with the number of mii buses.
 The record (struct bb_miiphy_bus) has the following fields/callbacks (see
 miiphy.h for details):
 
-char name[]            - The symbolic name that must be equal to the MII bus
-                         registered name
-int (*init)()          - Initialization function called at startup time (just
-                         before the Ethernet initialization)
+char name[]	       - The symbolic name that must be equal to the MII bus
+			 registered name
+int (*init)()	       - Initialization function called at startup time (just
+			 before the Ethernet initialization)
 int (*mdio_active)()   - Activate the MDIO pin as output
 int (*mdio_tristate)() - Activate the MDIO pin as input/tristate pin
 int (*set_mdio)()      - Write the MDIO pin
 int (*get_mdio)()      - Read the MDIO pin
 int (*set_mdc)()       - Write the MDC pin
-int (*delay)()         - Delay function
-void *priv             - Private data used by board specific code
+int (*delay)()	       - Delay function
+void *priv	       - Private data used by board specific code
 
 The board code will look like:
 
@@ -50,7 +50,7 @@ struct bb_miiphy_bus bb_miiphy_buses[] = {
  ...
 };
 int bb_miiphy_buses_num = sizeof(bb_miiphy_buses) /
-                          sizeof(bb_miiphy_buses[0]);
+			  sizeof(bb_miiphy_buses[0]);
 
 2009 Industrie Dial Face S.p.A.
      Luigi 'Comio' Mantellini <luigi.mantellini@idf-hit.com>
diff --git a/doc/README.drivers.eth b/doc/README.drivers.eth
index e06d3ad..e73e462 100644
--- a/doc/README.drivers.eth
+++ b/doc/README.drivers.eth
@@ -88,7 +88,7 @@ The return value for this function should be as follows:
 < 0 - failure (hardware failure, not probe failure)
 >=0 - number of interfaces detected
 
-You might notice that many drivers seem to use xxx_initialize() rather than 
+You might notice that many drivers seem to use xxx_initialize() rather than
 xxx_register().  This is the old naming convention and should be avoided as it
 causes confusion with the driver-specific init function.
 
diff --git a/doc/README.kwbimage b/doc/README.kwbimage
index 2a5b3b3..6dd942f 100644
--- a/doc/README.kwbimage
+++ b/doc/README.kwbimage
@@ -17,12 +17,12 @@ Command syntax:
 		to list the kwb image file details
 
 ./tools/mkimage -n <board specific configuration file> \
-                -T kwbimage -a <start address> -e <execution address> \
+		-T kwbimage -a <start address> -e <execution address> \
 		-d <input_raw_binary> <output_kwboot_file>
 
 for ex.
 ./tools/mkimage -n ./board/Marvell/openrd_base/kwbimage.cfg \
-                -T kwbimage -a 0x00600000 -e 0x00600000 \
+		-T kwbimage -a 0x00600000 -e 0x00600000 \
 		-d u-boot.bin u-boot.kwb
 
 kwimage support available with mkimage utility will generate kirkwood boot