Eric Lee / smarc-ti-linux-kernel

Download as
Browse Code ยป

Commit a6144bb9e7b4c82f7366bd74f8beac826f5f6b7f

Authored by Michael Witten
Committed by Jiri Kosina
1 parent a20e3a795b
Exists in master and in 20 other branches dlt-processor-sdk-linux-03.00.00.04, newt-ti-linux-3.12.y, processor-sdk-linux-01.00.00, processor-sdk-linux-02.00.01, smarc-ti-linux-3.12.10, smarc-ti-linux-3.12.y, smarc-ti-linux-3.14.y, smarc-ti-linux-3.15.y, smarc-ti-lsk-linux-4.1.y, smarct3x-processor-sdk-04.01.00.06, smarct3x-processor-sdk-linux-02.00.01, smarct3x-processor-sdk-linux-03.00.00.04, smarct4x-800-processor-sdk-linux-02.00.01, smarct4x-processor-sdk-04.01.00.06, smarct4x-processor-sdk-linux-02.00.01, smarct4x-processor-sdk-linux-03.00.00.04, ti-linux-3.12.y, ti-linux-3.14.y, ti-linux-3.15.y, ti-lsk-linux-4.1.y

README: Better comma usage 

For the most part, this commit simply introduces commas to
offset modifiers.

Signed-off-by: Michael Witten <mfwitten@gmail.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>

Showing 1 changed file with 8 additions and 8 deletions Side-by-side Diff

... ... @@ -137,7 +137,7 @@
137 137  
138 138 BUILD directory for the kernel:
139 139  
140   - When compiling the kernel all output files will per default be
  140 + When compiling the kernel, all output files will per default be
141 141 stored together with the kernel source code.
142 142 Using the option "make O=output/dir" allow you to specify an alternate
143 143 place for the output files (including .config).
144 144  
... ... @@ -145,13 +145,13 @@
145 145 kernel source code: /usr/src/linux-3.X
146 146 build directory: /home/name/build/kernel
147 147  
148   - To configure and build the kernel use:
  148 + To configure and build the kernel, use:
149 149 cd /usr/src/linux-3.X
150 150 make O=/home/name/build/kernel menuconfig
151 151 make O=/home/name/build/kernel
152 152 sudo make O=/home/name/build/kernel modules_install install
153 153  
154   - Please note: If the 'O=output/dir' option is used then it must be
  154 + Please note: If the 'O=output/dir' option is used, then it must be
155 155 used for all invocations of make.
156 156  
157 157 CONFIGURING the kernel:
... ... @@ -230,7 +230,7 @@
230 230 possible to do "make install" if you have lilo installed to suit the
231 231 kernel makefiles, but you may want to check your particular lilo setup first.
232 232  
233   - To do the actual install you have to be root, but none of the normal
  233 + To do the actual install, you have to be root, but none of the normal
234 234 build should require that. Don't take the name of root in vain.
235 235  
236 236 - If you configured any of the parts of the kernel as `modules', you
... ... @@ -238,7 +238,7 @@
238 238  
239 239 - Verbose kernel compile/build output:
240 240  
241   - Normally the kernel build system runs in a fairly quiet mode (but not
  241 + Normally, the kernel build system runs in a fairly quiet mode (but not
242 242 totally silent). However, sometimes you or other kernel developers need
243 243 to see compile, link, or other commands exactly as they are executed.
244 244 For this, use "verbose" build mode. This is done by inserting
... ... @@ -267,7 +267,7 @@
267 267 - Booting a kernel directly from a floppy without the assistance of a
268 268 bootloader such as LILO, is no longer supported.
269 269  
270   - If you boot Linux from the hard drive, chances are you use LILO which
  270 + If you boot Linux from the hard drive, chances are you use LILO, which
271 271 uses the kernel image as specified in the file /etc/lilo.conf. The
272 272 kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
273 273 /boot/bzImage. To use the new kernel, save a copy of the old image
... ... @@ -320,7 +320,7 @@
320 320 incomprehensible to you, but it does contain information that may
321 321 help debugging the problem. The text above the dump is also
322 322 important: it tells something about why the kernel dumped code (in
323   - the above example it's due to a bad kernel pointer). More information
  323 + the above example, it's due to a bad kernel pointer). More information
324 324 on making sense of the dump is in Documentation/oops-tracing.txt
325 325  
326 326 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
... ... @@ -328,7 +328,7 @@
328 328 sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred).
329 329 This utility can be downloaded from
330 330 ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/ .
331   - Alternately you can do the dump lookup by hand:
  331 + Alternately, you can do the dump lookup by hand:
332 332  
333 333 - In debugging dumps like the above, it helps enormously if you can
334 334 look up what the EIP value means. The hex value as such doesn't help