Eric Lee / smarc-ti-linux-kernel

Download as
Browse Code ยป

Commit f65e51d740688b8a0ad15cbde34974e6c4559972

Authored by Sylvestre Ledru
Committed by Linus Torvalds
1 parent 44a4dcf75c
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

Documentation: fix minor typos/spelling 

Fix some minor typos:
 * informations => information
 * there own => their own
 * these => this

Signed-off-by: Sylvestre Ledru <sylvestre.ledru@scilab.org>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Showing 24 changed files with 43 additions and 43 deletions Side-by-side Diff

Documentation/ABI/testing/sysfs-driver-hid-roccat-kone
Diff comments   View file @ f65e51d
... ... @@ -40,7 +40,7 @@
40 40 Date: March 2010
41 41 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
42 42 Description: The mouse can store 5 profiles which can be switched by the
43   - press of a button. A profile holds informations like button
  43 + press of a button. A profile holds information like button
44 44 mappings, sensitivity, the colors of the 5 leds and light
45 45 effects.
46 46 When read, these files return the respective profile. The
Documentation/ABI/testing/sysfs-driver-hid-roccat-koneplus
Diff comments   View file @ f65e51d
... ... @@ -33,7 +33,7 @@
33 33 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
34 34 Description: The mouse can store 5 profiles which can be switched by the
35 35 press of a button. A profile is split in settings and buttons.
36   - profile_buttons holds informations about button layout.
  36 + profile_buttons holds information about button layout.
37 37 When written, this file lets one write the respective profile
38 38 buttons back to the mouse. The data has to be 77 bytes long.
39 39 The mouse will reject invalid data.
... ... @@ -47,7 +47,7 @@
47 47 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
48 48 Description: The mouse can store 5 profiles which can be switched by the
49 49 press of a button. A profile is split in settings and buttons.
50   - profile_buttons holds informations about button layout.
  50 + profile_buttons holds information about button layout.
51 51 When read, these files return the respective profile buttons.
52 52 The returned data is 77 bytes in size.
53 53 This file is readonly.
... ... @@ -58,7 +58,7 @@
58 58 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
59 59 Description: The mouse can store 5 profiles which can be switched by the
60 60 press of a button. A profile is split in settings and buttons.
61   - profile_settings holds informations like resolution, sensitivity
  61 + profile_settings holds information like resolution, sensitivity
62 62 and light effects.
63 63 When written, this file lets one write the respective profile
64 64 settings back to the mouse. The data has to be 43 bytes long.
... ... @@ -73,7 +73,7 @@
73 73 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
74 74 Description: The mouse can store 5 profiles which can be switched by the
75 75 press of a button. A profile is split in settings and buttons.
76   - profile_settings holds informations like resolution, sensitivity
  76 + profile_settings holds information like resolution, sensitivity
77 77 and light effects.
78 78 When read, these files return the respective profile settings.
79 79 The returned data is 43 bytes in size.
Documentation/ABI/testing/sysfs-driver-hid-roccat-kovaplus
Diff comments   View file @ f65e51d
... ... @@ -52,7 +52,7 @@
52 52 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
53 53 Description: The mouse can store 5 profiles which can be switched by the
54 54 press of a button. A profile is split in settings and buttons.
55   - profile_buttons holds informations about button layout.
  55 + profile_buttons holds information about button layout.
56 56 When written, this file lets one write the respective profile
57 57 buttons back to the mouse. The data has to be 23 bytes long.
58 58 The mouse will reject invalid data.
... ... @@ -66,7 +66,7 @@
66 66 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
67 67 Description: The mouse can store 5 profiles which can be switched by the
68 68 press of a button. A profile is split in settings and buttons.
69   - profile_buttons holds informations about button layout.
  69 + profile_buttons holds information about button layout.
70 70 When read, these files return the respective profile buttons.
71 71 The returned data is 23 bytes in size.
72 72 This file is readonly.
... ... @@ -77,7 +77,7 @@
77 77 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
78 78 Description: The mouse can store 5 profiles which can be switched by the
79 79 press of a button. A profile is split in settings and buttons.
80   - profile_settings holds informations like resolution, sensitivity
  80 + profile_settings holds information like resolution, sensitivity
81 81 and light effects.
82 82 When written, this file lets one write the respective profile
83 83 settings back to the mouse. The data has to be 16 bytes long.
... ... @@ -92,7 +92,7 @@
92 92 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
93 93 Description: The mouse can store 5 profiles which can be switched by the
94 94 press of a button. A profile is split in settings and buttons.
95   - profile_settings holds informations like resolution, sensitivity
  95 + profile_settings holds information like resolution, sensitivity
96 96 and light effects.
97 97 When read, these files return the respective profile settings.
98 98 The returned data is 16 bytes in size.
Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra
Diff comments   View file @ f65e51d
... ... @@ -39,7 +39,7 @@
39 39 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
40 40 Description: The mouse can store 5 profiles which can be switched by the
41 41 press of a button. A profile is split in settings and buttons.
42   - profile_settings holds informations like resolution, sensitivity
  42 + profile_settings holds information like resolution, sensitivity
43 43 and light effects.
44 44 When written, this file lets one write the respective profile
45 45 settings back to the mouse. The data has to be 13 bytes long.
... ... @@ -54,7 +54,7 @@
54 54 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
55 55 Description: The mouse can store 5 profiles which can be switched by the
56 56 press of a button. A profile is split in settings and buttons.
57   - profile_settings holds informations like resolution, sensitivity
  57 + profile_settings holds information like resolution, sensitivity
58 58 and light effects.
59 59 When read, these files return the respective profile settings.
60 60 The returned data is 13 bytes in size.
... ... @@ -66,7 +66,7 @@
66 66 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
67 67 Description: The mouse can store 5 profiles which can be switched by the
68 68 press of a button. A profile is split in settings and buttons.
69   - profile_buttons holds informations about button layout.
  69 + profile_buttons holds information about button layout.
70 70 When written, this file lets one write the respective profile
71 71 buttons back to the mouse. The data has to be 19 bytes long.
72 72 The mouse will reject invalid data.
... ... @@ -80,7 +80,7 @@
80 80 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
81 81 Description: The mouse can store 5 profiles which can be switched by the
82 82 press of a button. A profile is split in settings and buttons.
83   - profile_buttons holds informations about button layout.
  83 + profile_buttons holds information about button layout.
84 84 When read, these files return the respective profile buttons.
85 85 The returned data is 19 bytes in size.
86 86 This file is readonly.
Documentation/ABI/testing/sysfs-platform-asus-laptop
Diff comments   View file @ f65e51d
... ... @@ -27,7 +27,7 @@
27 27 Contact: "Corentin Chary" <corentincj@iksaif.net>
28 28 Description:
29 29 Some models like the W1N have a LED display that can be
30   - used to display several informations.
  30 + used to display several items of information.
31 31 To control the LED display, use the following :
32 32 echo 0x0T000DDD > /sys/devices/platform/asus_laptop/
33 33 where T control the 3 letters display, and DDD the 3 digits display.
Documentation/devicetree/booting-without-of.txt
Diff comments   View file @ f65e51d
... ... @@ -138,7 +138,7 @@
138 138 section III, but, for example, the kernel does not require you to
139 139 create a node for every PCI device in the system. It is a requirement
140 140 to have a node for PCI host bridges in order to provide interrupt
141   -routing informations and memory/IO ranges, among others. It is also
  141 +routing information and memory/IO ranges, among others. It is also
142 142 recommended to define nodes for on chip devices and other buses that
143 143 don't specifically fit in an existing OF specification. This creates a
144 144 great flexibility in the way the kernel can then probe those and match
... ... @@ -385,7 +385,7 @@
385 385 among others, by kexec. If you are on an SMP system, this value
386 386 should match the content of the "reg" property of the CPU node in
387 387 the device-tree corresponding to the CPU calling the kernel entry
388   - point (see further chapters for more informations on the required
  388 + point (see further chapters for more information on the required
389 389 device-tree contents)
390 390  
391 391 - size_dt_strings
... ... @@ -553,7 +553,7 @@
553 553  
554 554 This tree is almost a minimal tree. It pretty much contains the
555 555 minimal set of required nodes and properties to boot a linux kernel;
556   -that is, some basic model informations at the root, the CPUs, and the
  556 +that is, some basic model information at the root, the CPUs, and the
557 557 physical memory layout. It also includes misc information passed
558 558 through /chosen, like in this example, the platform type (mandatory)
559 559 and the kernel command line arguments (optional).
Documentation/dvb/udev.txt
Diff comments   View file @ f65e51d
1 1 The DVB subsystem currently registers to the sysfs subsystem using the
2 2 "class_simple" interface.
3 3  
4   -This means that only the basic informations like module loading parameters
  4 +This means that only the basic information like module loading parameters
5 5 are presented through sysfs. Other things that might be interesting are
6 6 currently *not* available.
7 7  
Documentation/edac.txt
Diff comments   View file @ f65e51d
... ... @@ -311,7 +311,7 @@
311 311 'ce_noinfo_count'
312 312  
313 313 This attribute file displays the number of CEs that
314   - have occurred wherewith no informations as to which DIMM slot
  314 + have occurred wherewith no information as to which DIMM slot
315 315 is having errors. Memory is handicapped, but operational,
316 316 yet no information is available to indicate which slot
317 317 the failing memory is in. This count field should be also
Documentation/kernel-parameters.txt
Diff comments   View file @ f65e51d
... ... @@ -2478,8 +2478,8 @@
2478 2478 topology= [S390]
2479 2479 Format: {off | on}
2480 2480 Specify if the kernel should make use of the cpu
2481   - topology informations if the hardware supports these.
2482   - The scheduler will make use of these informations and
  2481 + topology information if the hardware supports this.
  2482 + The scheduler will make use of this information and
2483 2483 e.g. base its process migration decisions on it.
2484 2484 Default is on.
2485 2485  
Documentation/laptops/asus-laptop.txt
Diff comments   View file @ f65e51d
... ... @@ -61,7 +61,7 @@
61 61 Hotkeys are also reported as input keys (like keyboards) you can check
62 62 which key are supported using "xev" under X11.
63 63  
64   - You can get informations on the version of your DSDT table by reading the
  64 + You can get information on the version of your DSDT table by reading the
65 65 /sys/devices/platform/asus-laptop/infos entry. If you have a question or a
66 66 bug report to do, please include the output of this entry.
67 67  
... ... @@ -178,7 +178,7 @@
178 178 -----------
179 179  
180 180 Some models like the W1N have a LED display that can be used to display
181   - several informations.
  181 + several items of information.
182 182  
183 183 LED display works for the following models:
184 184 W1000N
Documentation/networking/batman-adv.txt
Diff comments   View file @ f65e51d
... ... @@ -72,7 +72,7 @@
72 72 # fragmentation gw_sel_class vis_mode
73 73  
74 74  
75   -There is a special folder for debugging informations:
  75 +There is a special folder for debugging information:
76 76  
77 77 # ls /sys/kernel/debug/batman_adv/bat0/
78 78 # gateways socket transtable_global vis_data
Documentation/s390/Debugging390.txt
Diff comments   View file @ f65e51d
... ... @@ -2273,7 +2273,7 @@
2273 2273 There is a lot of useful info in here best found by going in & having a look around,
2274 2274 so I'll take you through some entries I consider important.
2275 2275  
2276   -All the processes running on the machine have there own entry defined by
  2276 +All the processes running on the machine have their own entry defined by
2277 2277 /proc/<pid>
2278 2278 So lets have a look at the init process
2279 2279 cd /proc/1
Documentation/scsi/sym53c8xx_2.txt
Diff comments   View file @ f65e51d
... ... @@ -285,7 +285,7 @@
285 285  
286 286 7. Profiling information
287 287  
288   -This driver does not provide profiling informations as did its predecessors.
  288 +This driver does not provide profiling information as did its predecessors.
289 289 This feature was not this useful and added complexity to the code.
290 290 As the driver code got more complex, I have decided to remove everything
291 291 that didn't seem actually useful.
Documentation/sound/alsa/ALSA-Configuration.txt
Diff comments   View file @ f65e51d
... ... @@ -2229,7 +2229,7 @@
2229 2229  
2230 2230 /proc/asound/card#/pcm#[cp]/oss
2231 2231 -------------------------------
2232   - String "erase" - erase all additional informations about OSS applications
  2232 + String "erase" - erase all additional information about OSS applications
2233 2233 String "<app_name> <fragments> <fragment_size> [<options>]"
2234 2234  
2235 2235 <app_name> - name of application with (higher priority) or without path
Documentation/sound/oss/AudioExcelDSP16
Diff comments   View file @ f65e51d
1 1 Driver
2 2 ------
3 3  
4   -Informations about Audio Excel DSP 16 driver can be found in the source
  4 +Information about Audio Excel DSP 16 driver can be found in the source
5 5 file aedsp16.c
6 6 Please, read the head of the source before using it. It contain useful
7   -informations.
  7 +information.
8 8  
9 9 Configuration
10 10 -------------
... ... @@ -68,7 +68,7 @@
68 68 This driver supports the SC-6000 and SC-6600 based Gallant's sound card.
69 69 It don't support the Audio Excel DSP 16 III (try the SC-6600 code).
70 70 I'm working on the III version of the card: if someone have useful
71   -informations about it, please let me know.
  71 +information about it, please let me know.
72 72 For all the non-supported audio cards, you have to boot MS-DOS (or WIN95)
73 73 activating the audio card with the MS-DOS device driver, then you have to
74 74 <ctrl>-<alt>-<del> and boot Linux.
Documentation/sound/oss/README.ymfsb
Diff comments   View file @ f65e51d
... ... @@ -5,7 +5,7 @@
5 5 ============
6 6  
7 7 This code references YAMAHA's sample codes and data sheets.
8   - I respect and thank for all people they made open the informations
  8 + I respect and thank for all people they made open the information
9 9 about YMF7xx cards.
10 10  
11 11 And this codes heavily based on Jeff Garzik <jgarzik@pobox.com>'s
Documentation/video4linux/bttv/Insmod-options
Diff comments   View file @ f65e51d
1 1  
2   -Note: "modinfo <module>" prints various informations about a kernel
  2 +Note: "modinfo <module>" prints various information about a kernel
3 3 module, among them a complete and up-to-date list of insmod options.
4 4 This list tends to be outdated because it is updated manually ...
5 5  
Documentation/video4linux/bttv/Sound-FAQ
Diff comments   View file @ f65e51d
... ... @@ -8,7 +8,7 @@
8 8 sound is handled in slightly different ways on each board.
9 9  
10 10 To handle the grabber boards correctly, there is a array tvcards[] in
11   -bttv-cards.c, which holds the informations required for each board.
  11 +bttv-cards.c, which holds the information required for each board.
12 12 Sound will work only, if the correct entry is used (for video it often
13 13 makes no difference). The bttv driver prints a line to the kernel
14 14 log, telling which card type is used. Like this one:
Documentation/video4linux/et61x251.txt
Diff comments   View file @ f65e51d
... ... @@ -191,10 +191,10 @@
191 191 Description: Debugging information level, from 0 to 3:
192 192 0 = none (use carefully)
193 193 1 = critical errors
194   - 2 = significant informations
  194 + 2 = significant information
195 195 3 = more verbose messages
196 196 Level 3 is useful for testing only, when only one device
197   - is used at the same time. It also shows some more informations
  197 + is used at the same time. It also shows some more information
198 198 about the hardware being detected. This module parameter can be
199 199 changed at runtime thanks to the /sys filesystem interface.
200 200 Default: 2
Documentation/video4linux/sn9c102.txt
Diff comments   View file @ f65e51d
... ... @@ -214,10 +214,10 @@
214 214 Description: Debugging information level, from 0 to 3:
215 215 0 = none (use carefully)
216 216 1 = critical errors
217   - 2 = significant informations
  217 + 2 = significant information
218 218 3 = more verbose messages
219 219 Level 3 is useful for testing only. It also shows some more
220   - informations about the hardware being detected.
  220 + information about the hardware being detected.
221 221 This parameter can be changed at runtime thanks to the /sys
222 222 filesystem interface.
223 223 Default: 2
Documentation/video4linux/w9968cf.txt
Diff comments   View file @ f65e51d
... ... @@ -413,7 +413,7 @@
413 413 Description: Debugging information level, from 0 to 6:
414 414 0 = none (use carefully)
415 415 1 = critical errors
416   - 2 = significant informations
  416 + 2 = significant information
417 417 3 = configuration or general messages
418 418 4 = warnings
419 419 5 = called functions
Documentation/video4linux/zc0301.txt
Diff comments   View file @ f65e51d
... ... @@ -181,10 +181,10 @@
181 181 Description: Debugging information level, from 0 to 3:
182 182 0 = none (use carefully)
183 183 1 = critical errors
184   - 2 = significant informations
  184 + 2 = significant information
185 185 3 = more verbose messages
186 186 Level 3 is useful for testing only, when only one device
187   - is used at the same time. It also shows some more informations
  187 + is used at the same time. It also shows some information
188 188 about the hardware being detected. This module parameter can be
189 189 changed at runtime thanks to the /sys filesystem interface.
190 190 Default: 2
... ... @@ -261,7 +261,7 @@
261 261  
262 262 11. Credits
263 263 ===========
264   -- Informations about the chip internals needed to enable the I2C protocol have
  264 +- Information about the chip internals needed to enable the I2C protocol have
265 265 been taken from the documentation of the ZC030x Video4Linux1 driver written
266 266 by Andrew Birkett <andy@nobugs.org>;
267 267 - The initialization values of the ZC0301 controller connected to the PAS202BCB
arch/powerpc/mm/tlb_low_64e.S
Diff comments   View file @ f65e51d
... ... @@ -431,7 +431,7 @@
431 431 * The thing is, we know that in normal circumstances, this is
432 432 * always called as a second level tlb miss for SW load or as a first
433 433 * level TLB miss for HW load, so we should be able to peek at the
434   - * relevant informations in the first exception frame in the PACA.
  434 + * relevant information in the first exception frame in the PACA.
435 435 *
436 436 * However, we do need to double check that, because we may just hit
437 437 * a stray kernel pointer or a userland attack trying to hit those
arch/powerpc/platforms/Kconfig
Diff comments   View file @ f65e51d
... ... @@ -46,7 +46,7 @@
46 46 help
47 47 Support from booting from Open Firmware or yaboot using an
48 48 Open Firmware client interface. This enables the kernel to
49   - communicate with open firmware to retrieve system informations
  49 + communicate with open firmware to retrieve system information
50 50 such as the device tree.
51 51  
52 52 In case of doubt, say Y