All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hebbar <gururajakr@sanyo.co.in>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Remove gaps and whitespaces in README file
Date: Tue, 20 May 2008 02:25:00 -0700 (PDT)	[thread overview]
Message-ID: <17336468.post@talk.nabble.com> (raw)


Hi, 

Remove gaps and whitespaces in README file

Here in my company i cannot use git and hence no git-patch or git-mail. Will
see if i can convince them to allow git. sorry till then 

Regards 
Gururaja 

Signed off by: Gururaja Hebbar <gururajakr@sanyo.co.in> 


diff -purN u-boot-1.3.3/README u-boot-1.3.3-modified/README
--- u-boot-1.3.3/README	2008-05-19 03:47:11.000000000 -0700
+++ u-boot-1.3.3-modified/README	2008-05-20 13:58:47.656250000 -0700
@@ -180,15 +180,15 @@ Directory Hierarchy:
 - dtt		Digital Thermometer and Thermostat drivers
 - examples	Example code for standalone applications, etc.
 - include	Header Files
-- lib_arm	Files generic to ARM	 architecture
-- lib_avr32	Files generic to AVR32	 architecture
-- lib_generic	Files generic to all	 architectures
-- lib_i386	Files generic to i386	 architecture
-- lib_m68k	Files generic to m68k	 architecture
-- lib_mips	Files generic to MIPS	 architecture
-- lib_nios	Files generic to NIOS	 architecture
+- lib_arm	Files generic to ARM architecture
+- lib_avr32	Files generic to AVR32 architecture
+- lib_generic	Files generic to all architectures
+- lib_i386	Files generic to i386 architecture
+- lib_m68k	Files generic to m68k architecture
+- lib_mips	Files generic to MIPS architecture
+- lib_nios	Files generic to NIOS architecture
 - lib_ppc	Files generic to PowerPC architecture
-- lib_sparc	Files generic to SPARC	 architecture
+- lib_sparc	Files generic to SPARC architecture
 - libfdt	Library files to support flattened device trees
 - net		Networking code
 - post		Power On Self Test
@@ -608,7 +608,7 @@ The following options need to be configu
 		CONFIG_CMD_NAND		* NAND support
 		CONFIG_CMD_NET		  bootp, tftpboot, rarpboot
 		CONFIG_CMD_PCI		* pciinfo
-		CONFIG_CMD_PCMCIA		* PCMCIA support
+		CONFIG_CMD_PCMCIA	* PCMCIA support
 		CONFIG_CMD_PING		* send ICMP ECHO_REQUEST to network
 					  host
 		CONFIG_CMD_PORTIO	* Port I/O
@@ -618,7 +618,7 @@ The following options need to be configu
 		CONFIG_CMD_SCSI		* SCSI Support
 		CONFIG_CMD_SDRAM	* print SDRAM configuration information
 					  (requires CONFIG_CMD_I2C)
-		CONFIG_CMD_SETGETDCR	  Support for DCR Register access
+		CONFIG_CMD_SETGETDCR  Support for DCR Register access
 					  (4xx only)
 		CONFIG_CMD_SPI		* SPI serial bus support
 		CONFIG_CMD_USB		* USB support
@@ -1697,14 +1697,14 @@ The following options need to be configu
 
 Legacy uImage format:
 
-  Arg	Where			When
+  Arg	Where				When
     1	common/cmd_bootm.c	before attempting to boot an image
-   -1	common/cmd_bootm.c	Image header has bad	 magic number
+   -1	common/cmd_bootm.c	Image header has bad magic number
     2	common/cmd_bootm.c	Image header has correct magic number
-   -2	common/cmd_bootm.c	Image header has bad	 checksum
+   -2	common/cmd_bootm.c	Image header has bad checksum
     3	common/cmd_bootm.c	Image header has correct checksum
-   -3	common/cmd_bootm.c	Image data   has bad	 checksum
-    4	common/cmd_bootm.c	Image data   has correct checksum
+   -3	common/cmd_bootm.c	Image data has bad checksum
+    4	common/cmd_bootm.c	Image data has correct checksum
    -4	common/cmd_bootm.c	Image is for unsupported architecture
     5	common/cmd_bootm.c	Architecture check OK
    -5	common/cmd_bootm.c	Wrong Image Type (not kernel, multi)
@@ -1716,11 +1716,11 @@ Legacy uImage format:
    -9	common/cmd_bootm.c	Unsupported OS (not Linux, BSD, VxWorks, QNX)
 
     9	common/image.c		Start initial ramdisk verification
-  -10	common/image.c		Ramdisk header has bad	   magic number
-  -11	common/image.c		Ramdisk header has bad	   checksum
+  -10	common/image.c		Ramdisk header has bad magic number
+  -11	common/image.c		Ramdisk header has bad checksum
    10	common/image.c		Ramdisk header is OK
-  -12	common/image.c		Ramdisk data   has bad	   checksum
-   11	common/image.c		Ramdisk data   has correct checksum
+  -12	common/image.c		Ramdisk data has bad checksum
+   11	common/image.c		Ramdisk data has correct checksum
    12	common/image.c		Ramdisk verification complete, start loading
   -13	common/image.c		Wrong Image Type (not PPC Linux Ramdisk)
    13	common/image.c		Start multifile image verification
@@ -1762,7 +1762,7 @@ Legacy uImage format:
    48	common/cmd_ide.c	reading Image Header from IDE device OK
   -49	common/cmd_ide.c	Image header has bad magic number
    49	common/cmd_ide.c	Image header has correct magic number
-  -50	common/cmd_ide.c	Image header has bad	 checksum
+  -50	common/cmd_ide.c	Image header has bad checksum
    50	common/cmd_ide.c	Image header has correct checksum
   -51	common/cmd_ide.c	Error reading Image from IDE device
    51	common/cmd_ide.c	reading Image from IDE device OK





http://www.nabble.com/file/p17336468/uboot-1.3.3-README_remove_whitespace.diff
uboot-1.3.3-README_remove_whitespace.diff 
-- 
View this message in context: http://www.nabble.com/-PATCH--Remove-gaps-and-whitespaces-in-README-file-tp17336468p17336468.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

             reply	other threads:[~2008-05-20  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20  9:25 Hebbar [this message]
2008-05-20  9:32 ` [U-Boot-Users] [PATCH] Remove gaps and whitespaces in README file Wolfgang Denk
2008-05-20  9:36   ` Hebbar
2008-05-20 12:29     ` Wolfgang Denk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17336468.post@talk.nabble.com \
    --to=gururajakr@sanyo.co.in \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.